From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Teach rebase -i about --preserve-merges
Date: Tue, 26 Jun 2007 02:15:48 +0200 [thread overview]
Message-ID: <f5plgb$uvl$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0706251859270.4059@racer.site
Johannes Schindelin wrote:
> *2*: git-rebase without --interactive is inherently patch based (at
> least at the moment), and therefore merges cannot be preserved.
What about "git rebase --merge"?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-06-26 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 17:59 [PATCH 3/3] Teach rebase -i about --preserve-merges Johannes Schindelin
2007-06-26 0:15 ` Jakub Narebski [this message]
2007-06-26 2:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='f5plgb$uvl$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