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

Re: git bisect with history manipulation

From
Sean <seanlkml@sympatico.ca>
Date
Oct 23, 2006, 16:25 UTC
Message-ID
<BAYC1-PASMTP110AEA1A20D3DF82D9BCE8AE000@CEZ.ICE>
In-Reply-To
<ehiq2l$lkq$1@sea.gmane.org>

On Mon, 23 Oct 2006 18:19:56 +0200 Jakub Narebski <jnareb@gmail.com> wrote:

Show 6 quoted lines
> Sean wrote:
> 
> > $ patch < patch1
> 
> We have git-apply for that (sometimes git-am would work on whole
> series of patches).

Point taken. git-rebase and git-cherrypick may also be appropriate to snag the commits from another branch rather than reapplying them from patches. In fact you may already have a branch that works which contains just your patches on top of it. I was trying to make the example as clear as possible rather than exhaustive.

Sean
Previous: Jakub NarebskiNext: Catalin Marinas
Message 7 of 8 in “git bisect with history manipulation”
  1. Kalle PokkiOct 23, 2006
  2. Linus TorvaldsOct 23, 2006
  3. Jakub NarebskiOct 23, 2006
  4. Linus TorvaldsOct 23, 2006
  5. SeanOct 23, 2006
  6. Jakub NarebskiOct 23, 2006
  7. SeanOct 23, 2006
  8. Catalin MarinasOct 23, 2006

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.