(Sorry about my tardiness in replying; also, moved bug-gnulib to BCC and added bug-findutils)
On Nov 27, 2007 12:06 PM, Jim Meyering <[EMAIL PROTECTED]> wrote: > I'm feel about CVS the way I've felt about K&R C for years now. > It's worth supporting if doing so is really easy (i.e., "automatic"), but > when it starts to require too much extra work, then I leave it behind. > > If you're interested in switching findutils to git -- or even just > mirroring cvs-to-git for starters, let me know and I'll set it up. I dipped my toe in the waters this spring, by using git at repo.or.cz to support the Google Summer of Code. That worked OK, so I have progressed to using a private git repository to organise patches before mailing them to [EMAIL PROTECTED] Once they've had an airing there (Eric being the principal reviewer) I apply them to the Savannah CVS repository. Then I use git-cvsimport to update repo.or.cz and my local git repositories. My experience has been positive. I still can't always visualise the effect of a git command before running it, but I've had remarkably few "Drat. Now what do I do?" moments. Based on this I am reasonably content to plan to migrate from CVS to git. However, before doing that I want to concentrate my available efforts to releasing findutils-4.4.0. This will allow me to create a fresh development branch and fold the Summer of Code contributions into it. They're valuable but potentially destabilising, so I don't want to merge them into the current relatively stable 4.3.x tree. James.