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

Re: RFC: "git config -l" should not expose sensitive information

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 20, 2012, 18:37 UTC
Message-ID
<7vfw306048.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20121220155229.GA6008@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Yeah. Thanks for a dose of sanity. I was really trying not to say "the
> given advice is bad, and we cannot help those people". But I think you
> are right; the only sensible path is for the user to inspect the output
> before posting it.
True.
Previous: Jeff KingNext: Toralf Förster
Message 5 of 10 in “RFC: "git config -l" should not expose sensitive information”
  1. Toralf FörsterDec 17, 2012
  2. Jeff KingDec 20, 2012
  3. Aaron SchrabDec 20, 2012
  4. Jeff KingDec 20, 2012
  5. Junio C HamanoDec 20, 2012
  6. Toralf FörsterDec 20, 2012
  7. Michael HaggertyDec 20, 2012
  8. Jeff KingDec 20, 2012
  9. Junio C HamanoDec 20, 2012
  10. Andrew ArdillDec 20, 2012

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.