git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: kernel cherry UN-picking?

From
JSJosef Sipek <jsipek@fsl.cs.sunysb.edu>
Date
May 15, 2007, 02:39 UTC
Message-ID
<20070515023941.GA20340@filer.fsl.cs.sunysb.edu>
In-Reply-To
<20070511145509.09f3c354.akpm@linux-foundation.org>
On Fri, May 11, 2007 at 02:55:09PM -0700, Andrew Morton wrote:
Show 26 quoted lines
> On Fri, 11 May 2007 17:31:14 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
> 
> > So, I merge the next batch of net driver patches.  After I merge a PPP 
> > patch, deep in the pile-o-patches, Andrew says "I shouldn't have sent 
> > that to you, don't apply it"  ;-)
> 
> I'm bad.
> 
> > Right now, my process for reversing this damage is to start over: 
> > create a new branch, manually double-click the mouse on each commit in 
> > the "damaged" branch, and git-cherrypick it.  Very, very time consuming 
> > when you have more than a couple commits.
> > 
> > Is there a better way?
> > Is there any way to say "cherrypick all commits except <these>"?
> 
> Let me refactor your question more usefully.  What we want is quilt-export
> and quilt-import.  And I really mean that: commands called git-quilt-export
> and git-quilt-import.
> 
> coz then, your problem becomes
> 
> 	git-quilt-export
> 	<delete one line from the series file>
> 	git-quilt-import
<shameless plug>
You can use Guilt:
$ guilt-init
$ guilt-import-commit <the bad commit hash>^..
$ $EDITOR .git/patches/$branch/series
	# remove the offending line from the series file
$ guilt-push -a
$ rm -rf .git/patches/$branch
</shameless plug>
Josef "Jeff" Sipek.
-- 
All science is either physics or stamp collecting.
		- Ernest Rutherford
Previous: Jeff GarzikNext: Junio C Hamano
Message 4 of 9 in “kernel cherry UN-picking?”
  1. Jeff GarzikMay 11, 2007
  2. Andrew MortonMay 11, 2007
  3. Jeff GarzikMay 11, 2007
  4. Josef SipekMay 15, 2007
  5. Junio C HamanoMay 11, 2007
  6. Junio C HamanoMay 11, 2007
  7. Junio C HamanoMay 11, 2007
  8. Jan HarkesMay 12, 2007
  9. Jan HarkesMay 12, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.