bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] cvs not working?


From: Christian Anthon
Subject: Re: [Bug-gnubg] cvs not working?
Date: Mon, 1 Jun 2009 16:58:47 +0200

There is a script with the obvious name cvs2svn that facilitates the change . I believe it is fairly good and straightforward to use. Savannah allows the raw cvs to be downloaded and has support for svn.
 
I'm mildly indifferent between cvs and svn for gnubg, though I would certainly go with svn for a new project. One point for svn is that it should make it easier for us to move files around to get a better directory structure without breaking the history.
 
Christian.

On Mon, Jun 1, 2009 at 9:49 AM, Jonathan Kinsey <address@hidden> wrote:
When it comes back we could consider switching from cvs to svn. I use svn at
work and it's much better than cvs (imo), the atomic commits would probably
remove the need of the Changelog file - the svn log would be very similar to
this file.

I'm not sure how easy switching it over would be (or 100% sure it's possible).

Jon

Øystein Johansen wrote:
> Jonathan Kinsey wrote:
>> Is it just me or is cvs down?
>
> I got this message from the savannah folks:
>
>> Hi,
>>
>> Savannah experienced a filesystem corruption and is now halted.
>>
>> The FSF sysadmins (who have physical access to the hardware) are
>> alerted and will investigate, and possibly restore from backup.
>>
>> To be safe, do not expect the service to be restored before 24h,
>> although we'll do our best to do so :)
>>
>> The website, CVS/SVN/Git/Hg/Bzr, and the download area are affected.
>> The mailing lists and webpages are not affected.
>>
>> -- The Savannah Hackers
>
> Sent: 29/05/2009 10:07 to address@hidden
>
> -Øystein
>
>





Get the New Internet Explore 8 Optimised for MSN. Download Now

_______________________________________________
Bug-gnubg mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/bug-gnubg



reply via email to

[Prev in Thread] Current Thread [Next in Thread]