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

Re: mktree: multiple same-named objects

From
Jeff King <peff@peff.net>
Date
Aug 27, 2014, 16:24 UTC
Message-ID
<20140827162425.GA1432@peff.net>
In-Reply-To
<xmqqk35uezd0.fsf@gitster.dls.corp.google.com>
On Wed, Aug 27, 2014 at 08:17:15AM -0700, Junio C Hamano wrote:
Show 10 quoted lines
> I am somewhat against outright removing the capability to write out
> invalid objects deliberately from these low level tools, because we
> would need a way to easily reproduce bugs in end-user facing tools
> by other people who claim to produce Git objects, but I would agree
> that by default that should be forbidden.
> 
> In other words, two things must happen; improve checks when these
> low level debugging aid tools are creating objects, and allow
> bypassing these additional checks with "--experiment" option or
> something.

Yeah, definitely. I had imagined it as "--strict" and "--no-strict", with flipping the default to "--strict" at some point (I do not see a reason anybody would not want it in normal use, but if we are worried, we can even go slowly on flipping the default).

-Peff
Previous: Junio C Hamano
Message 6 of 6 in “mktree: multiple same-named objects”
  1. David TurnerAug 27, 2014
  2. Duy NguyenAug 27, 2014
  3. David TurnerAug 27, 2014
  4. Jeff KingAug 27, 2014
  5. Junio C HamanoAug 27, 2014
  6. Jeff KingAug 27, 2014

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.