From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
git@vger.kernel.org, remi.galan-alfonso@ensimag.grenoble-inp.fr
Subject: Re: What's cooking in git.git (Oct 2015, #01; Mon, 5)
Date: Tue, 06 Oct 2015 08:32:13 +0200 [thread overview]
Message-ID: <vpqr3l8pkwi.fsf@grenoble-inp.fr> (raw)
In-Reply-To: <xmqqoagcwocp.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 05 Oct 2015 22:35:50 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> On 06.10.15 00:59, Junio C Hamano wrote:
>>> * gr/rebase-i-drop-warn (2015-10-02) 2 commits
>>> - rebase-i: loosen over-eager check_bad_cmd check
>>> - rebase-i: explicitly accept tab as separator in commands
>>>
>>> "git rebase -i" had a minor regression recently, which stopped
>>> considering a line that begins with an indented '#' in its insn
>>> sheet not a comment, which is now fixed.
>>>
>>> Will merge to 'next'.
>> This is breaking using a non-gnu sed, which doesn't handle "\t"...
>
> Thanks for catching this, and the other one in the stalled section,
> before they hit 'next'.
>
>> The solution is to replace "\t" with a literal TAB.
>
> Obviously correct ;-) Will squash in.
Indeed. Thanks.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2015-10-06 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 22:59 What's cooking in git.git (Oct 2015, #01; Mon, 5) Junio C Hamano
2015-10-06 3:02 ` Torsten Bögershausen
2015-10-06 5:55 ` Junio C Hamano
2015-10-06 19:30 ` Mike Rappazzo
2015-10-06 4:45 ` Torsten Bögershausen
2015-10-06 5:35 ` Junio C Hamano
2015-10-06 6:32 ` Matthieu Moy [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=vpqr3l8pkwi.fsf@grenoble-inp.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
--cc=tboegi@web.de \
/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