git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean <seanlkml@sympatico.ca>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git bisect with history manipulation
Date: Mon, 23 Oct 2006 12:25:27 -0400	[thread overview]
Message-ID: <BAYC1-PASMTP110AEA1A20D3DF82D9BCE8AE000@CEZ.ICE> (raw)
Message-ID: <20061023122527.4c095580.seanlkml@sympatico.ca> (raw)
In-Reply-To: <ehiq2l$lkq$1@sea.gmane.org>

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

> 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

  reply	other threads:[~2006-10-23 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a425f86c0610230718i556537dei9a4b2a5fa8d7f003@mail.gmail.com>
2006-10-23 14:22 ` git bisect with history manipulation Kalle Pokki
2006-10-23 15:34   ` Linus Torvalds
2006-10-23 15:42     ` Jakub Narebski
2006-10-23 15:59       ` Linus Torvalds
     [not found]   ` <20061023114738.f77efec3.seanlkml@sympatico.ca>
2006-10-23 15:47     ` Sean
2006-10-23 16:19       ` Jakub Narebski
     [not found]         ` <20061023122527.4c095580.seanlkml@sympatico.ca>
2006-10-23 16:25           ` Sean [this message]
2006-10-23 16:21       ` Catalin Marinas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAYC1-PASMTP110AEA1A20D3DF82D9BCE8AE000@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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.
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 NNTP newsgroup(s).