From: Junio C Hamano <gitster@pobox.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2016, #08; Fri, 29)
Date: Mon, 02 May 2016 10:21:10 -0700 [thread overview]
Message-ID: <xmqqshy0v0jd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160430004741.GA16900@yexl-desktop> (Ye Xiaolong's message of "Sat, 30 Apr 2016 08:47:41 +0800")
Ye Xiaolong <xiaolong.ye@intel.com> writes:
> On Fri, Apr 29, 2016 at 03:04:58PM -0700, Junio C Hamano wrote:
>>* xy/format-patch-base (2016-04-26) 4 commits
>> - format-patch: introduce format.useAutoBase configuration
>> - format-patch: introduce --base=auto option
>> - format-patch: add '--base' option to record base tree info
>> - patch-ids: make commit_patch_id() a public helper function
>>
>> "git format-patch" learned a new "--base" option to record what
>> (public, well-known) commit the original series was built on in
>> its output.
>>
>> Looking close to be ready.
>> ($gmane/292622).
>
> Not quite sure about this status, anything else I need to do other
> than the follow-up patch which to do the enhancement feature
> suggested by Stefan?
I thought that we all agreed that enhancing it with even more
heuristics would be nice to have but lack of them does not block
what is already in the series from progressing without them?
I was planning to hold this for in 'pu' for a while, until others
review them with fresh eyes to make sure there is no have any
glaring errors or leaks, and then merge them to 'next' and
eventually down to 'master', while accepting follow-up patches on
top but as a separate "enhancement" effort.
prev parent reply other threads:[~2016-05-02 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 22:04 What's cooking in git.git (Apr 2016, #08; Fri, 29) Junio C Hamano
2016-04-30 0:47 ` Ye Xiaolong
2016-05-02 17:21 ` Junio C Hamano [this message]
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=xmqqshy0v0jd.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=xiaolong.ye@intel.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).