Hi, On Mon, 19 May 2008, Matthew Ogilvie wrote: > I perceive one remaining big issue for git-cvsserver to be a good > replacement for real CVS: The ability to properly support "cvs update -r > VERSION", where VERSION could be any branch, tag, CVS version number, or > git commit hash. Git-cvsserver can partially support this by checking > out a totally different sandbox as "cvs checkout VERSION" (notice no > -r), but without the ability to switch versions in place, that is an > awkward workaround at best. I might be missing something obvious, but would it not be better to _not_ check out anything, but serve every object straight from the object database (possibly with CR/LF mangling)? Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
