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

Re: [RFC] a tale of Git 2.5, ssh transport and GIT_* environment variables

From
Jeff King <peff@peff.net>
Date
Sep 4, 2015, 21:44 UTC
Message-ID
<20150904214454.GA18320@sigill.intra.peff.net>
In-Reply-To
<xmqqpp1yf3qe.fsf@gitster.mtv.corp.google.com>
On Fri, Sep 04, 2015 at 11:18:01AM -0700, Junio C Hamano wrote:
Show 9 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > It shouldn't be necessary for $GIT_DIR, but it makes sense for other git
> > variables. E.g., with "AcceptEnv GIT_*", "git -c" config is propagated.
> > E.g.:
> > ...
> 
> Just to make sure I got you correctly, you are saying that "we
> propagate, but that is not correct. We should stop doing so", right?

Exactly. We do not propagate config over git:// or http:// (because we do not share our environment). Nor do we do so over same-machine connections (because we explicitly clean the environment). So ssh:// is the odd duck.

-Peff
Previous: Giuseppe BilottaNext: Jeff King
Message 7 of 12 in “[RFC] a tale of Git 2.5, ssh transport and GIT_* environment variables”
  1. Giuseppe BilottaSep 4, 2015
  2. Jeff KingSep 4, 2015
  3. Giuseppe BilottaSep 4, 2015
  4. Jeff KingSep 4, 2015
  5. Junio C HamanoSep 4, 2015
  6. Giuseppe BilottaSep 4, 2015
  7. Jeff KingSep 4, 2015
  8. git_connect: clear GIT_* environment for sshJeff King, Sep 4, 2015
  9. Giuseppe BilottaSep 5, 2015
  10. git_connect: clarify conn->use_shell flagJeff King, Sep 8, 2015
  11. Junio C HamanoSep 8, 2015
  12. Jeff KingSep 8, 2015

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.