From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: Han-Wen Nienhuys via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Han-Wen Nienhuys <hanwenn@gmail.com>
Subject: Re: [PATCH] t1404: mark directory/file conflict tests with REFFILES
Date: Mon, 29 Nov 2021 09:59:09 -0800 [thread overview]
Message-ID: <xmqqsfve3ksy.fsf@gitster.g> (raw)
In-Reply-To: <CAFQ2z_OTc41g9YgA70W8NCWKWRaRs41EJVZFihmTiPnZFOiEEw@mail.gmail.com> (Han-Wen Nienhuys's message of "Mon, 29 Nov 2021 11:57:28 +0100")
Han-Wen Nienhuys <hanwen@google.com> writes:
> 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.
next prev parent reply other threads:[~2021-11-29 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 15:57 [PATCH] t1404: mark directory/file conflict tests with REFFILES Han-Wen Nienhuys via GitGitGadget
2021-11-26 7:39 ` Junio C Hamano
2021-11-29 10:57 ` Han-Wen Nienhuys
2021-11-29 17:59 ` Junio C Hamano [this message]
2021-11-29 18:20 ` [PATCH v2] " Han-Wen Nienhuys via GitGitGadget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsfve3ksy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hanwen@google.com \
--cc=hanwenn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).