Re: [Netatalk-devel] Development is stuck over here, let's branch 2-1 away or switch to git

[Frank L. <fra...@go...>]

2010/4/20 didier <dga...@ma...>:
> Hi,
> Le lundi 19 avril 2010 à 17:25 +0200, Frank Lahm a écrit :
>> >> Thus I'll:
>> >> - again wipe the current git tree
>> >> - reimport current CVS, this time with every branch in there
>> >
>> > Here you go, this time with all cruft intact:
>> > <http://netatalk.git.sourceforge.net/git/gitweb.cgi?p=netatalk/netatalk;a=summary>
>> >
> Ok, looks great.

;)

>> >>> What do we do for docs and test suite trees?
>> >>
>> >> Move to git too.
>> >
>> > I've already setup the repos and load them soon:
>> > <http://netatalk.git.sourceforge.net/git/gitweb-index.cgi>
>>
>> Now they're all there (besided atalkconf which I'm thinking of moving
>> to the main netatalk repro, possibly inside bin)
>>
>> Theoretically we could completely switch over now.
>
> Agree.

As CVS is still a moving target, I suggest the following procedure for
the switch:
- release 2.1 next Monday
On Tuesday:
- freeze CVS
- resync CVS to git
- shutdown CVS
- start using git

>> copy of the current complete CVS data which I'd like to send to
>> several people as tarball just in case (Didier, HAT, Andew) ...
>
> I already have a daily rsynced copy of sourceforge cvs tree.

Ah, ok. In that case I'll save the bandwidth. ;)