From: Johannes Sixt <j.sixt@viscovery.net>
To: Pieter de Bie <frim@frim.nl>
Cc: git@vger.kernel.org
Subject: Re: [BUG?] git rebase -i
Date: Fri, 14 Dec 2007 08:30:49 +0100 [thread overview]
Message-ID: <47623129.2030303@viscovery.net> (raw)
In-Reply-To: <2791F15A-EB72-4FE4-8DB3-7A4B4DCB07B3@frim.nl>
Pieter de Bie schrieb:
> Another thing to note is
> that the 1.5.4.rc0 tries to apply 215 patches, while the 1.5.3.5 tries
> to apply 206 patches.
This is to be expected: 1.5.3.5 counts the comment lines at the top of the
action file, of which there are exactly 9, 1.5.4.rc0 does not count them.
-- Hannes
next prev parent reply other threads:[~2007-12-14 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 1:21 [BUG?] git rebase -i Pieter de Bie
2007-12-14 7:30 ` Johannes Sixt [this message]
2007-12-17 16:04 ` Pieter de Bie
2007-12-17 16:59 ` [PATCH] rebase -p -i: handle "no changes" gracefully Johannes Schindelin
2007-12-17 20:23 ` Junio C Hamano
2007-12-17 21:01 ` [PATCH w/ test] " Johannes Schindelin
2007-12-18 20:24 ` Junio C Hamano
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=47623129.2030303@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=frim@frim.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).