From: Ben Curtis <nospam@nowsci.com>
Date: Sat, 18 Jan 2020 16:34:20 GMT
Subject: Re: [PATCH] commit: replace rebase/sequence booleans with single pick_state enum
Message-ID: <bb0e232924305697596743d3fa93d5bf3b0e8d4d.camel@nowsci.com>
In-Reply-To: <17b57e7f-7f3c-abab-1da6-d2e5c9ff893d@gmail.com>

On Fri, 2020-01-17 at 20:01 +0000, Phillip Wood wrote:
> Hi Ben
> 
> On 17/01/2020 13:45, Ben Curtis via GitGitGadget wrote:
> > From: Ben Curtis <nospam@nowsci.com>
> > 
> > In 116a408,
> 
> That commit is no longer in pu, it has been replaced by 430b75f720 
> ("commit: give correct advice for empty commit during a rebase", 
> 2019-12-06). There is now a preparatory commit 8d57f75749 ("commit:
> use 
> enum value for multiple cherry-picks", 2019-12-06) which replaces
> the 
> booleans with an enum. I need to reroll the series 
> (pw/advise-rebase-skip) that contains them, if you've got any
> comments 
> please let me know.
> 
> Best Wishes
> 
> Phillip
> 

Hi Phillip,

Thank you for the feedback, I assume that means my patch is no longer
required?

Also, is there a formal issue assignment method with `git`? I hopped on
this particular issue on GitGitGadget to get my feet wet here but was
not sure if there was a separate maintained list to track overlap like
the above.

Thanks!
Ben