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

Re: [RFC][PATCH] Fix assumption that git is installed in a standard place on the remote end ssh

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 19, 2007, 00:16 UTC
Message-ID
<Pine.LNX.4.64.0706190114110.4059@racer.site>
In-Reply-To
<20070615154000.GK14677@menevado.ms.com>
Hi,
On Fri, 15 Jun 2007, Kevin Green wrote:
> I'm thinking I like the env var idea much more though.  I can just 
> export it in my shell and it works in both cases.

And it completely breaks down when you have more than one remotes. Or when you cd to another project with another remote. Or etc. IOW it is fragile.

Clearly, the config approach is the only one which makes sense. This information is so closely coupled to a specific remote that you should store it right where you store all the other remote information, too.

Ciao, Dscho

Previous: Raimund BauerNext: Kevin Green
Message 5 of 7 in “Fix assumption that git is installed in a standard place on the remote end ssh”
  1. Kevin GreenJun 15, 2007
  2. Julian PhillipsJun 15, 2007
  3. Kevin GreenJun 15, 2007
  4. Raimund BauerJun 15, 2007
  5. Johannes SchindelinJun 19, 2007
  6. Kevin GreenJun 22, 2007
  7. Johannes SchindelinJun 22, 2007

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.