From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: replacing a bad commit
Date: Mon, 05 Feb 2007 17:38:18 +0100 [thread overview]
Message-ID: <eq7mf0$lb0$1@sea.gmane.org> (raw)
In-Reply-To: 20070205153949.GT14499@daga.cl
Blu Corater wrote:
> Here is the situation. Upstream realeses tarballs once in a while. I
> maintain local modifications. Every time upstream releases a tarball, I
> fast forward the 'upstream' branch, and merge into 'local' branch. My
> tree, currently, looks somewhat like this:
>
> o---o---o <--topic2
> |
> | o---o---o <--topic1
> | /
> o---o---C---A---o---o <--local
> / / /
> / / /
> o---o---o---B <--upstream
>
> Problem is, B should have been merged into 'local', at A, but I just
> realized it wasn't (probably due to my own stupidity).
>
> I need to correct A, i.e. merge with B, but keeping the branches already
> in flux, and propagating the changes due to the merge to them. In short,
> replace A with a properly merged A'.
>
> I tried branching from C and merging with B, then rebasing topic branches,
> but then I am not sure how to rebase 'local'to eliminate A.
Try using
$ git rebase --onto A' A local
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-05 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 15:39 replacing a bad commit Blu Corater
2007-02-05 16:38 ` Jakub Narebski [this message]
2007-02-05 19:53 ` Blu Corater
2007-02-05 20:02 ` Shawn O. Pearce
2007-02-05 20:21 ` Blu Corater
2007-02-05 20:38 ` Jakub Narebski
2007-02-05 20:53 ` Blu Corater
2007-02-05 20:58 ` Shawn O. Pearce
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='eq7mf0$lb0$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).