From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] rebase-i: do not get fooled by a log message ending with backslash
Date: Tue, 6 Jul 2010 13:57:06 -0500 [thread overview]
Message-ID: <20100706185706.GA7296@burratino> (raw)
In-Reply-To: <1278397631-20658-3-git-send-email-gitster@pobox.com>
Junio C Hamano wrote:
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Posix mandates the -r option to replace the less convenient ‘line’
utility. read -r is part of SVR4.2[1] so any vaguely Posix-ish sh
should have it (i.e., not Solaris /bin/sh, but that’s okay).
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
(Not tested, since I don’t have access to any non-Linux installations
nowadays.)
[1] http://www.in-ulm.de/~mascheck/bourne/
prev parent reply other threads:[~2010-07-06 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 6:27 [PATCH 0/2] rebase-i minifixes Junio C Hamano
2010-07-06 6:27 ` [PATCH 1/2] rebase-i: style fix Junio C Hamano
2010-07-06 6:27 ` [PATCH 2/2] rebase-i: do not get fooled by a log message ending with backslash Junio C Hamano
2010-07-06 18:57 ` Jonathan Nieder [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=20100706185706.GA7296@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).