git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ulrik <ulrik.sverdrup@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] Invalid rebase command leaves unclean status
Date: Wed, 19 Dec 2007 01:47:12 +0100	[thread overview]
Message-ID: <a1b6cb1b0712181647v34822692t4a3d88f90cd7346@mail.gmail.com> (raw)

Hello git list

A bug in rebase -i: A typo in the command (for example in the branch
name) still makes later invocations of rebase think a rebase is
already in process.

I found this bug in master, and it was already reported to the mailing
list under version 1.5.3.5, but there were no follow-ups to that mail.
I'm using 1.5.3.7 and it is still present, and looking at the maint
branch it does not seem to be mentioned in post-x.3.7 changes there.
So I am now reporting this bug again. I'm sorry for not checking this
in master, I'll have to ask someone on the list to do that.

Original email:
http://marc.info/?l=git&m=119410951019002&w=2
Date:       2007-11-03 17:04:51
Message-ID: 200711031804.52259.elendil () planet ! nl

# A sample session:
# Invoking rebase with a typo, there is no "muster" branch
$ git rebase -i muster
fatal: Needed a single revision
Invalid base
$ git rebase -i master
Interactive rebase already started
$ git rebase --abort
fatal: Needed a single revision
# Even though rebase --abort reports an error, rebase's internal state
is now cleared

Regards,
Ulrik Sverdrup

             reply	other threads:[~2007-12-19  0:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19  0:47 ulrik [this message]
2007-12-19  7:42 ` [BUG] Invalid rebase command leaves unclean status Wincent Colaiuta
  -- strict thread matches above, loose matches on Subject: below --
2007-11-03 17:04 Frans Pop

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=a1b6cb1b0712181647v34822692t4a3d88f90cd7346@mail.gmail.com \
    --to=ulrik.sverdrup@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).