Re: [PATCH] commit: replace rebase/sequence booleans with single pick_state enum

git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed

From: Ben Curtis <nospam@nowsci.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>,
	phillip.wood@dunelm.org.uk,
	Ben Curtis via GitGitGadget <gitgitgadget@gmail.com>
Subject: Re: [PATCH] commit: replace rebase/sequence booleans with single pick_state enum
Date: Sat, 18 Jan 2020 11:34:20 -0500	[thread overview]
Message-ID: <bb0e232924305697596743d3fa93d5bf3b0e8d4d.camel@nowsci.com> (raw)
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

next prev parent reply	other threads:[~2020-01-18 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 13:45 [PATCH] commit: replace rebase/sequence booleans with single pick_state enum Ben Curtis via GitGitGadget
2020-01-17 14:29 ` Derrick Stolee
2020-01-17 15:46   ` Ben Curtis
2020-01-17 20:01 ` Phillip Wood
2020-01-18 16:34   ` Ben Curtis [this message]
2020-01-20 17:09     ` Phillip Wood
2020-01-20 21:11       ` Johannes Schindelin

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=bb0e232924305697596743d3fa93d5bf3b0e8d4d.camel@nowsci.com \
    --to=nospam@nowsci.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=stolee@gmail.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).