From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
Rene Moser <mail@renemoser.net>,
git@vger.kernel.org
Subject: Re: Bug: file named - on git commit
Date: Mon, 28 Jan 2013 12:51:53 -0800 [thread overview]
Message-ID: <7vy5fduj2u.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130128204140.GA7759@google.com> (Jonathan Nieder's message of "Mon, 28 Jan 2013 12:41:40 -0800")
Jonathan Nieder <jrnieder@gmail.com> writes:
> Thomas Rast wrote:
>> Rene Moser <mail@renemoser.net> writes:
>
>>> Found a little issue in git version 1.7.9.5 if a file named "-", causing
>>> "git commit" to read from stdin.
>>>
>>> (So you must hit ctrl-d or ctrl-c to finish the commit.)
> [...]
>> This was fixed by Junio around 4682d85 (diff-index.c: "git diff" has no
>> need to read blob from the standard input, 2012-06-27), which is
>> included starting with v1.7.12 and the v1.7.11.3 maint release. Please
>> upgrade.
>
> Should upgrade-averse folks stuck on 1.7.10.y (like Debian 7.0, which
> is currently in the release candidate stage) take this fix? Do you
> happen to know of any other fixes such people would want?
FYI, the fix referred to in this thread are three-patch series that
forked from 1.7.6.6, so it should be trivial to merge it even to
such an old version.
The topic-branch workflow shines ;-)
next prev parent reply other threads:[~2013-01-28 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 10:38 Bug: file named - on git commit Rene Moser
2013-01-28 10:56 ` Matthieu Moy
2013-01-28 10:58 ` Duy Nguyen
2013-01-28 11:05 ` Thomas Rast
2013-01-28 11:19 ` [CLOSED FIXED] " Rene Moser
2013-01-28 20:41 ` Jonathan Nieder
2013-01-28 20:51 ` Junio C Hamano [this message]
2013-01-28 21:01 ` Junio C Hamano
2013-02-04 17:43 ` Junio C Hamano
2013-02-04 19:32 ` Jonathan Nieder
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=7vy5fduj2u.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mail@renemoser.net \
--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).