[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] help with CVS
|
Thanks Thomas,
If you don't mind opening it up today (even for a limited time window) I'll
try to dig a little into potential issues with the structural setup of our
respective repos.
Cheers
Todd
Thomas Hallgren
<thomas@xxxxxxx>
Sent by: To
buckminster-dev-b Buckminster developer discussions
ounces@xxxxxxxxxx <buckminster-dev@xxxxxxxxxxx>
g cc
Subject
02/19/2008 10:22 Re: [buckminster-dev] help with CVS
AM
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
No, I don't normally keep those ports open. But I can enable it again.
- thomas
Todd_Lee@xxxxxxxx wrote:
> Hi again Thomas,
>
> I was just going to take a look at the test setup that you created to
> confirm things like structure etc, but it seems that anonymous access to
> the tada repo isn't available (actually, it's reporting a timeout).
Should
> I still be able to access the following CVSROOT? (
> :pserver:anonymous@xxxxxxxxxxx:/cvsroot/test)
>
> Thanks
> Todd
>
>
>
>
> Thomas Hallgren
> <thomas@xxxxxxx>
> Sent by:
To
> buckminster-dev-b Buckminster developer discussions
> ounces@xxxxxxxxxx <buckminster-dev@xxxxxxxxxxx>
> g
cc
>
>
Subject
> 02/15/2008 05:35 Re: [buckminster-dev] help with
CVS
> PM
>
>
> Please respond to
> Buckminster
> developer
> discussions
> <buckminster-dev@
> eclipse.org>
>
>
>
>
>
>
> Hi Todd,
>
> Todd_Lee@xxxxxxxx wrote:
>
>> Oh, and so as not to create any wild goose chases, I did find docs last
>> night that confirmed that eclipse cvs should be fine with cvs going all
>> the way back to 1.11.1, so I'm assuming our 1.11.3 shouldn't be a
>>
> problem.
>
> It should not. And if Eclipse can do things like check-out, then
> Buckminster should be fine too. Our
> CVS support is just a thin layer on top of everything that is included in
> the Eclipse CVS team provider.
>
>
>> If you have any other suggestions, please feel free to fire them off.
>>
>>
> The only thing I can think of at this point is to make really sure that
the
> repositories (the one I
> published) and yours are structured the same way.
>
>
>
>> One question - is there any way to get more debug info out of the
>> resolution stage? I have all three log settings in the prefs set to full
>> DEBUG and there's still not a whole lot of information in the console or
>> the .metadata/.log file.
>>
>> It would probably be helpful if the debug statements actually printed
>> out checks for the files inside the cvs path that buckminster uses to
>> poll for metadata for a given component type. Could give us a better
>> idea of where it's failing?
>>
>>
> Right. Cases like this really highlights the need for more extensive
> logging. I'll see what I can do
> about that. You're my only eyes into what's happening here so it seems
fair
> that I help you see some
> more relevant info :-)
>
>
> Regards,
> Thomas Hallgren
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
>
> AMI Semiconductor - "Silicon Solutions for the Real World"
> NOTICE:
> This electronic message contains information that may be confidential or
privileged. The information is intended for the use of the individual or
entity named above. If you are not the intended recipient, please be aware
that any disclosure, copying, distribution or use of the contents of this
information is prohibited. If you received this electronic message in
error, please notify the sender and delete the copy you received.
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev
AMI Semiconductor - "Silicon Solutions for the Real World"
NOTICE:
This electronic message contains information that may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic message in error, please notify the sender and delete the copy you received.
