From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Rast <trast@student.ethz.ch>, git@vger.kernel.org
Subject: Re: [Bug?] rebase-i marking the last entry for edit gives a barf?
Date: Sun, 28 Mar 2010 12:14:54 -0600 [thread overview]
Message-ID: <fabb9a1e1003281114r3253cd0eg67a917fb67331af9@mail.gmail.com> (raw)
In-Reply-To: <7vd3yo2vno.fsf@alter.siamese.dyndns.org>
Heya,
On Sun, Mar 28, 2010 at 11:39, Junio C Hamano <gitster@pobox.com> wrote:
> This was after marking both commits in a two-patch series for "edit" in
> rebase -i, running "commit --amend; rebase --continue; commit --amend";
> saying "rebase --continue" at this point gave this error.
I noticed the same as well, so it's not just you :).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-03-28 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 17:39 [Bug?] rebase-i marking the last entry for edit gives a barf? Junio C Hamano
2010-03-28 18:14 ` Sverre Rabbelier [this message]
2010-03-28 19:36 ` [PATCH] rebase -i: make post-rewrite work for 'edit' Thomas Rast
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=fabb9a1e1003281114r3253cd0eg67a917fb67331af9@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
/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).