From: Junio C Hamano <gitster@pobox.com>
To: Chen BoJun <bojun.cbj@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2022, #03; Sat, 12)
Date: Tue, 15 Feb 2022 15:56:38 -0800 [thread overview]
Message-ID: <xmqqfsojznt5.fsf@gitster.g> (raw)
In-Reply-To: <20220215020923.38168-1-bojun.cbj@gmail.com> (Chen BoJun's message of "Tue, 15 Feb 2022 10:09:23 +0800")
Chen BoJun <bojun.cbj@gmail.com> writes:
>> * cb/clear-quarantine-early-on-all-ref-update-errors (2022-02-01) 1 commit
>> - receive-pack: purge temporary data if no command is ready to run
>>
>> Check if "receive-pack" will do any ref updates (various conditions
>> could reject a push) before received objects are taken out of the
>> temporary directory used for quarantine purposes, so that a push
>> that is known-to-fail will not leave crufts that a future "gc"
>> needs to clean up.
>>
>> Will merge to 'next'.
>> source: <20220129063538.24038-1-bojun.cbj@gmail.com>
>
> I noticed that the merged patch was v2, not v3 which I sent last week. Apart
> from a more complete commit message, there is no change in patch v3. So merge
> patch v2 is OK.
Sorry, my mistake. The log message in the updated one reads a lot
better.
next prev parent reply other threads:[~2022-02-15 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 9:24 What's cooking in git.git (Feb 2022, #03; Sat, 12) Junio C Hamano
2022-02-14 20:01 ` Jonathan Tan
2022-02-14 21:16 ` Junio C Hamano
2022-02-15 2:09 ` Chen BoJun
2022-02-15 23:56 ` Junio C Hamano [this message]
2022-02-15 16:24 ` js/use-builtin-add-i (was Re: What's cooking in git.git (Feb 2022, #03; Sat, 12)) Phillip Wood
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=xmqqfsojznt5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bojun.cbj@gmail.com \
--cc=git@vger.kernel.org \
/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).