Hi Alban,
On Thu, Jun 14, 2018 at 1:24 PM, Alban Gruin <alban.gr...@gmail.com> wrote:
> Le 14/06/2018 à 22:14, Junio C Hamano a écrit :
>> Alban Gruin <alban.gr...@gmail.com> writes:
>>
>>> diff --git a/builtin/rebase--helper.c b/builtin/rebase--helper.c
>>> index ded5e291d..d2990b210 100644
>>> --- a/builtin/rebase--helper.c
>>> +++ b/builtin/rebase--helper.c
>>> @@ -12,12 +12,12 @@ static const char * const builtin_rebase_helper_usage[]
>>> = {
>>> int cmd_rebase__helper(int argc, const char **argv, const char *prefix)
>>> {
>>> struct replay_opts opts = REPLAY_OPTS_INIT;
>>> - unsigned flags = 0, keep_empty = 0, rebase_merges = 0, write_edit_todo
>>> = 0;
>>> + unsigned flags = 0, keep_empty = 0, rebase_merges = 0;
>>
>> Sorry, but where does "write_edit_todo = 0" in the preimage come from?
>>
>
> It comes from my conversion of append_todo_help()[0], on which this
> series is based.
>
> [0]
> https://public-inbox.org/git/20180607103012.22981-1-alban.gr...@gmail.com/
Given that both Junio and I had the same basic question, you'll
probably want to put dependency information into your cover letters.
If a series applies on master, then this isn't needed. But if it
requires other changes that are in a topic in next or pu, you can name
the topic that it depends upon (e.g. ag/rebase-p, as from the "What's
cooking" emails or you can grab them as branchnames from
git://github.com/gitster/git). If the dependency is something that
Junio hasn't picked up yet, provide a link to the other submission.
Others may have additional suggestions here...
