Paul Eggert <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]:/$PROJ.git co -d $PROJ HEAD whenever: "$(GIT_DIR=/git-repo-for-$PROJ git config gitcvs.pserver.enabled)" = 1
