git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-cvs*: Make building (and testing) of CVS interface scripts optionally selectable

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 7, 2011, 23:50 UTC
Message-ID
<7vei8o46jy.fsf@alter.siamese.dyndns.org>
In-Reply-To
<robbat2-20110107T225413-429815896Z@orbis-terrarum.net>
"Robin H. Johnson" <robbat2@gentoo.org> writes:
Show 8 quoted lines
> On Fri, Jan 07, 2011 at 04:01:48PM -0600, Jonathan Nieder wrote:
>> This explanation seems quite odd to me.  Are you saying we can't rely
>> on the 'cvs' name being "taken" and should live in fear that someone
>> will implement an incompatible utility with the same name?  Did that
>> actually happen?
> Not in the linked bug report, but it does explain a previous bug I had
> seen, where a user had a little script in /usr/local/bin that complained
> at him whenever he ran 'cvs', so he would learn to migrate away faster.

I suspect that NO_CVS is not the best way to help a person who is trying to wean herself off of cvs by having a phony cvs in a directory that is early on the $PATH (be it $HOME/bin/cvs or /usr/local/bin/cvs). Before ceasing to actively build more histories in cvs, it would help to have an access to git-cvsimport and friends to salvage what's already there, no?

A change that models after PERL_PATH, not after NO_PERL, would be a more appropriate thing to do for that particular purpose.

I still think the patch itself is a worthy thing to have, so everything above is a tangent that is orthogonal to what your patch tries to do, though.

Previous: Robin H. JohnsonNext: Junio C Hamano
Message 4 of 6 in “git-cvs*: Make building (and testing) of CVS interface scripts optionally selectable”
  1. git-cvs*: Make building (and testing) of CVS interface scripts optionally selectableRobin H. Johnson, Jan 7, 2011
  2. Jonathan NiederJan 7, 2011
  3. Robin H. JohnsonJan 7, 2011
  4. Junio C HamanoJan 7, 2011
  5. Junio C HamanoJan 7, 2011
  6. Robin H. JohnsonJan 7, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.