From: Frans Pop <elendil@planet.nl>
To: git@vger.kernel.org
Subject: [BUG] Invalid rebase command leaves unclean status
Date: Sat, 3 Nov 2007 18:04:51 +0100 [thread overview]
Message-ID: <200711031804.52259.elendil@planet.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
The first command results in the creation of an empty .dotest-merge/output
file which blocks any next attempt to do an interactive rebase until it is
manually removed.
$ git rebase master -i
Invalid branchname: -i
$ git rebase -i master
Interactive rebase already started
$ ls .git/.dotest-merge/
output
$ cat .git/.dotest-merge/output
$ rm -r .git/.dotest-merge/
$ git rebase -i master
<works>
This is with git version 1.5.3.5.
Cheers,
Frans Pop
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-11-03 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 17:04 Frans Pop [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-19 0:47 [BUG] Invalid rebase command leaves unclean status ulrik
2007-12-19 7:42 ` Wincent Colaiuta
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=200711031804.52259.elendil@planet.nl \
--to=elendil@planet.nl \
--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).