From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2024, #01; Mon, 3)
Date: Tue, 04 Jun 2024 11:31:58 -0700 [thread overview]
Message-ID: <xmqqa5k0v9sx.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZRzR1Nfqa1KA04W2EzAq0nM5Fr1p7PEfsukidL0-RsWGQ@mail.gmail.com> (Karthik Nayak's message of "Tue, 4 Jun 2024 08:07:01 +0000")
Karthik Nayak <karthik.188@gmail.com> writes:
> Hello Junio,
>
> Junio C Hamano <gitster@pobox.com> writes:
>
> [snip]
>
>> * kn/update-ref-symref (2024-05-30) 7 commits
>> - update-ref: add support for 'symref-update' command
>> - reftable: pick either 'oid' or 'target' for new updates
>> - update-ref: add support for 'symref-create' command
>> - update-ref: add support for 'symref-delete' command
>> - update-ref: add support for 'symref-verify' command
>> - refs: create and use `ref_update_expects_existing_old_ref()`
>> - Merge branch 'kn/ref-transaction-symref' into kn/update-ref-symref
>>
>> "git update-ref --stdin" learned to handle transactional updates of
>> symbolic-refs.
>>
>> Expecting a (hopefully minor and final) reroll.
>> source: <20240514124411.1037019-1-knayak@gitlab.com>
>
> I did send in a v3 recently:
The above is the v3 on May 30th. I do not know offhand if all the
review comments on the previous round have been addressed in this
iteration? Perhaps this needs to be marked as "Needs review" to
make sure, but I forgot to update it.
Thanks.
next prev parent reply other threads:[~2024-06-04 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 6:16 What's cooking in git.git (Jun 2024, #01; Mon, 3) Junio C Hamano
2024-06-04 8:06 ` Patrick Steinhardt
2024-06-04 8:07 ` Karthik Nayak
2024-06-04 18:31 ` Junio C Hamano [this message]
2024-06-04 8:52 ` Jeff King
2024-06-04 18:36 ` Junio C Hamano
2024-06-05 8:35 ` Jeff King
2024-06-05 16:30 ` Junio C Hamano
2024-06-04 8:59 ` Christian Couder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa5k0v9sx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@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.
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 NNTP newsgroup(s).