# [Bug?] "am --abort" broken?

3 messages from 2013-06-12 to 2013-06-13. Participants: Junio C Hamano, Ramkumar Ramachandra.
Thread: https://gitlist.dev/t/34118

## Junio C Hamano, 2013-06-12 22:38

Subject: [Bug?] "am --abort" broken?
Message-ID: <7vsj0nymyd.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vsj0nymyd.fsf%40alter.siamese.dyndns.org

```
This is somewhat minor but will confuse people who do not know how
to manually recover from.  Start "am" without giving an input file
by mistake:

    $ git am ;# no input file
    ^C

At this point, you are still in "am" session; completion will tell
you that you are in a middle of "am/rebase".  A more recent way to
get out of this is to use "am --abort", but you get this:

    $ git am --abort
    Resolve operation not in progress, we are not resuming.

"git am" from 'maint' will help you get out of it, or you can do it
the old fashioned way:

    $ rm -fr .git/rebase-apply

I think this is a recent breakage after merging the topic to add
"rebase --autostash", but I haven't looked into it yet.

```

## Ramkumar Ramachandra, 2013-06-13 04:00

Subject: Re: [Bug?] "am --abort" broken?
Message-ID: <CALkWK0ksCupC183X-XDwCcscHkQXq9whxxYeWLjR2FpH50ycHA@mail.gmail.com>
URL: https://gitlist.dev/e/CALkWK0ksCupC183X-XDwCcscHkQXq9whxxYeWLjR2FpH50ycHA%40mail.gmail.com
In-Reply-To: <7vsj0nymyd.fsf@alter.siamese.dyndns.org>

```
Junio C Hamano wrote:
>     $ git am ;# no input file
>     ^C
>
>     $ git am --abort
>     Resolve operation not in progress, we are not resuming.

I tried it on git 1.8.3, and this only incidentally "seems" to half-work (?)

% git am
^C
% git am --abort
cat: /home/artagnon/src/git/.git/rebase-apply/next: No such file or directory
% git status
# On branch master
# Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
#
nothing to commit, working directory clean

In the process of aborting, it blew away one commit!

> I think this is a recent breakage after merging the topic to add
> "rebase --autostash", but I haven't looked into it yet.

Yes, I can confirm that my topic introduced this bug, and I apologize
for not having caught it.  I'm looking into the problem.

Thanks.

```

## Junio C Hamano, 2013-06-13 04:17

Subject: Re: [Bug?] "am --abort" broken?
Message-ID: <7v7ghyy795.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7v7ghyy795.fsf%40alter.siamese.dyndns.org
In-Reply-To: <CALkWK0ksCupC183X-XDwCcscHkQXq9whxxYeWLjR2FpH50ycHA@mail.gmail.com>

```
Ramkumar Ramachandra <artagnon@gmail.com> writes:

>> I think this is a recent breakage after merging the topic to add
>> "rebase --autostash", but I haven't looked into it yet.
>
> Yes, I can confirm that my topic introduced this bug, and I apologize
> for not having caught it.  I'm looking into the problem.

No need to apologize; nobody caught it during the review.

And thanks for volunteering.

```