From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: another git rebase -i problem
Date: Thu, 14 Feb 2008 14:02:28 +0100 [thread overview]
Message-ID: <20080214130228.GB28472@digi.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802141232070.30505@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> On Thu, 14 Feb 2008, Uwe Kleine-König wrote:
>
> > After applying the patch below, the test fails. [describes a case where
> > all patches were applied upstream already]
>
> This is by design. If no patches are to be applied, there is nothing you
> can do interactively. And git rebase -i should tell you as much:
>
> Nothing to do
>
> Maybe it should say
>
> There is nothing you can rebase interactively
>
> But I don't like that.
>
> Alternatively, git rebase -i could reset --hard to upstream, but I don't
> like that either: if I rebase -i, it is because I want to reorder/arrange
> patches. If there is no patch to be rearranged, I did something wrong.
Ah, OK this disqualifies my test case, but the problem is real:
diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh
index e5ed745..f0499e6 100755
--- a/t/t3404-rebase-interactive.sh
+++ b/t/t3404-rebase-interactive.sh
@@ -362,4 +362,11 @@ test_expect_success 'rebase with a file named HEAD in worktree' '
'
+test_expect_success 'rebase patch already merged' '
+
+ git checkout -b branch4 twerp &&
+ FAKE_LINES="1 2 4 3" git rebase -i branch3
+
+'
+
test_done
Best regards
Uwe
--
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962
next prev parent reply other threads:[~2008-02-14 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 9:37 another git rebase -i problem Uwe Kleine-König
2008-02-14 12:35 ` Johannes Schindelin
2008-02-14 13:02 ` Uwe Kleine-König [this message]
2008-02-14 15:39 ` Johannes Schindelin
2008-02-15 8:10 ` Uwe Kleine-König
2008-02-15 9:21 ` Uwe Kleine-König
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=20080214130228.GB28472@digi.com \
--to=uwe.kleine-koenig@digi.com \
--cc=Johannes.Schindelin@gmx.de \
--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).