From: Danh Doan <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)
Date: Tue, 19 Nov 2019 16:38:04 +0700 [thread overview]
Message-ID: <20191119093804.GA22048@danh.dev> (raw)
In-Reply-To: <xmqqftikxs4z.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On 2019-11-19 16:05:48+0900, Junio C Hamano <gitster@pobox.com> wrote:
> * dd/rebase-merge-reserves-onto-label (2019-11-19) 1 commit
> - sequencer: handle rebase-merge for "onto" message
> (this branch uses js/rebase-r-safer-label.)
>
> The logic to avoid duplicate label names generated by "git rebase
> --rebase-merges" forgot that the machinery itself uses "onto" as a
> label name, which must be avoided by auto-generated labels, which
> has been corrected.
>
> Will merge to 'next'.
You've merged my v1 PATCH which is full of typo in commit message.
Please queue my v2 PATCH instead.
--
Danh
next prev parent reply other threads:[~2019-11-19 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 7:05 What's cooking in git.git (Nov 2019, #03; Tue, 19) Junio C Hamano
2019-11-19 9:38 ` Danh Doan [this message]
2019-11-20 2:52 ` Junio C Hamano
2019-11-19 17:58 ` SZEDER Gábor
2019-11-20 3:02 ` Junio C Hamano
2019-11-20 13:58 ` Derrick Stolee
2019-11-21 0:36 ` Junio C Hamano
2019-11-21 11:10 ` Derrick Stolee
2019-11-22 5:42 ` Junio C Hamano
2019-11-19 18:01 ` ag/sequencer-todo-updates , was " Alban Gruin
2019-11-19 20:41 ` Jonathan Tan
2019-11-20 3:03 ` Junio C Hamano
2019-11-21 8:17 ` Alban Gruin
2019-11-23 0:47 ` Alban Gruin
2019-11-20 23:32 ` Denton Liu
2019-11-21 0:39 ` Junio C Hamano
2019-11-23 20:35 ` Philippe Blain
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=20191119093804.GA22048@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).