Re: FYI: commits-to-cvs disabled (switching to git)

[Sylvain Beucler]

On Thu, Sep 20, 2007 at 08:12:51AM +0200, Jim Meyering wrote:
> Paul Eggert <address@hidden> wrote:
> > Jim Meyering <address@hidden> writes:
> >> I'll turn off cvs soon, probably tomorrow.
> >
> > By "turn off cvs" do you mean to disable even read-only access to old
> > versions?
> 
> No, of course not.
> Just as checking the box added "GIT" to some web menus,
> I presume that unchecking the CVS box will remove it from the
> menus.  Hmm.. but actually we don't want to remove it, but
> rather adjust the message so it points to the git-cvsserver
> checkout information.
> 
> > I hope not; I still have a bunch of old source trees,
> > checked out from CVS, that I occasionally need to do a "cvs diff" on.
> 
> You don't mind the "cvs diff" delays?
> It's easy to move such trees to git.
> You could store them all in a single directory (each committed to a
> different private branch), or in separate directories (not necessarily
> committed) each cloned-locally to share the underlying repository
> disk space.
> 
> Even in the second case, you really have to use a separate branch
> for each tree.  Otherwise, you'd run into trouble when updating.
> 
> So, I *won't* be turning off CVS *access*,
> but we do need to find a way to update the cvs-checkout instructions.
> 
> ---------------------------------------------------------------
> Sylvain, would it make sense to add code to say that this is the way
> to use CVS to check out $PROJ:
> 
> cvs -d :pserver:address@hidden:/$PROJ.git co -d $PROJ HEAD
> 
> whenever:
> 
> "$(GIT_DIR=/git-repo-for-$PROJ git config gitcvs.pserver.enabled)" = 1

For my project I still partially use CVS, plus I'd like to enable "git
pserver" for all projects, plus there's currently no way for the
frontend to know if git pserver is enabled - so, with the
multiplication of repositories we instead need some some Savane code
to describe all repositories attached to a project and they relate to
each others. Currently I don't have time to code this because we're
short of people to review submitted projects at Savannah, so I'd
welcome contributions (either in code, either in project approvals).

-- 
Sylvain