From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: git@vger.kernel.org
Cc: Steffen Nurpmeso <steffen@sdaoden.eu>
Subject: Re: 2.25.0: git rebase -i fails to --continue with staged data
Date: Sat, 01 Feb 2020 19:59:38 +0100 [thread overview]
Message-ID: <20200201185938.ACP7-%steffen@sdaoden.eu> (raw)
In-Reply-To: <20200201183619.tUTI7%steffen@sdaoden.eu>
Steffen Nurpmeso wrote in <20200201183619.tUTI7%steffen@sdaoden.eu>:
No. Sorry for the noise, it was my fault, i reversed the todo
list, and therefore, after having committed something new that
_should_ have been placed in between two "e"dited changesets,
i was in fact after them, and git did correctly point out it had
no idea on what to do with staged data.
Sorry.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
prev parent reply other threads:[~2020-02-01 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 18:36 2.25.0: git rebase -i fails to --continue with staged data Steffen Nurpmeso
2020-02-01 18:59 ` Steffen Nurpmeso [this message]
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=20200201185938.ACP7-%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--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).