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

Re: [PATCH] t1404: mark directory/file conflict tests with REFFILES

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 29, 2021, 17:59 UTC
Message-ID
<xmqqsfve3ksy.fsf@gitster.g>
In-Reply-To
<CAFQ2z_OTc41g9YgA70W8NCWKWRaRs41EJVZFihmTiPnZFOiEEw@mail.gmail.com>
Han-Wen Nienhuys <hanwen@google.com> writes:
Show 10 quoted lines
> On Fri, Nov 26, 2021 at 8:39 AM Junio C Hamano <gitster@pobox.com> wrote:
>
>> And presumably, without REFFILES prerequisite, these operations
>> would be supported?  E.g. we can have 'main' branch, with 'main/1',
>> 'main/2',... refs, at the same time, with reftable?  That would be
>> quite interesting.
>
> The storage format allows D/F conflicts, but transactions are checked
> for not creating new D/F conflicts (depending on
> the value of reftable_write_options.skip_name_check).

OK. Then once we let reffiles wither and die over time, hopefully we can flip the bit and allow us to be in an interesting world ;-)

Nice.
Previous: Han-Wen NienhuysNext: Han-Wen Nienhuys via GitGitGadget
Message 4 of 5 in “t1404: mark directory/file conflict tests with REFFILES”
  1. t1404: mark directory/file conflict tests with REFFILESHan-Wen Nienhuys via GitGitGadget, Nov 25, 2021
  2. Junio C HamanoNov 26, 2021
  3. Han-Wen NienhuysNov 29, 2021
  4. Junio C HamanoNov 29, 2021
  5. t1404: mark directory/file conflict tests with REFFILESHan-Wen Nienhuys via GitGitGadget, Nov 29, 2021

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.