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

Re: [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates

From
IMIngo Molnar <mingo@elte.hu>
Date
Oct 12, 2011, 16:29 UTC
Message-ID
<20111012162947.GC31857@elte.hu>
In-Reply-To
<20111012141939.GA25085@sigill.intra.peff.net>
* Jeff King <peff@peff.net> wrote:
Show 7 quoted lines
> > It's really useful for a painless UI flow to disambiguate failure 
> > messages into clearly actionable variants.
> 
> I agree. I think some people are concerned with leaking information 
> about which repos exist and how they are configured. That is 
> probably not a big problem for a public site like kernel.org, 
> though.

Well, a gitconfig option could be provided to not leak that small amount of info - but it would otherwise be weird for an OSS SCM to default to a behavior that only makes sense with closed source, right? :-)

Thanks,
	Ingo
Previous: Jeff King
Message 3 of 3 in “Re: [PATCH 00/20] [GIT PULL][v3.2] tracing: queued updates”
  1. Ingo MolnarOct 12, 2011
  2. Jeff KingOct 12, 2011
  3. Ingo MolnarOct 12, 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.