Heiko Voigt <hvo...@hvoigt.net> writes:
> Thats a good idea. Can send a patch, but I noticed that your change is
> already in next and my change has not been picked up. So I am unsure if
> I should base my patches on next or if Junio wants to keep your change?
When you noticed something you want to touch up in 'next' but not in
'master', please try to find which topic the target of your
touching-up comes from.
git log --first-parent <other options> master..next
I often use --oneline for <other options>, because I am reasonably
familiar with the topics in 'next', but people may start from "git
blame" output, finding the commit that left the text you are
touching up, then where it was merged to 'next'. That would give
you
commit 59dbd5834007c1e4dff25770da095babcb69a009
Merge: 679f992 508a285
Author: Junio C Hamano <gits...@pobox.com>
Date: Tue Jul 19 13:43:44 2016 -0700
Merge branch 'rs/submodule-config-code-cleanup' into next
Code cleanup.
* rs/submodule-config-code-cleanup:
submodule-config: use explicit empty string instead of strbuf in
config_from()
The second parent 508a285c (submodule-config: use explicit empty
string instead of strbuf in config_from(), 2016-07-19) is a good
place to base your patch.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
