From: "Jan Krüger" <jk@jk.gs>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] log-tree: use custom line terminator in line termination mode
Date: Tue, 01 May 2012 01:28:28 +0200 [thread overview]
Message-ID: <4F9F201C.40509@jk.gs> (raw)
In-Reply-To: <7vd36oesjr.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
On 05/01/2012 12:58 AM, Junio C Hamano wrote:
> Having said that, are we sure that
>
> printf "add bar\0initial"
>
> works per specification, or merely works by accident in some
> implementation?
I don't know for certain. In these cases I go by what dash (Debian's sh
implementation) does. To quote its manpage:
"Only features designated by POSIX, plus a few Berkeley extensions, are
being incorporated into this shell."
It does support this syntax for printf. That's enough for me personally.
Is it enough for everyone? I don't know.
-Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2012-04-30 23:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:58 git log -z still outputting newlines? Randal L. Schwartz
2012-04-30 18:34 ` Andreas Schwab
2012-04-30 19:02 ` Thomas Rast
2012-04-30 18:45 ` [PATCH] log-tree: use custom line terminator in line termination mode Jan Krüger
2012-04-30 19:36 ` Junio C Hamano
2012-04-30 20:28 ` [PATCH v2] " Jan Krüger
2012-04-30 22:58 ` Junio C Hamano
2012-04-30 23:28 ` Jan Krüger [this message]
2012-05-01 0:28 ` Andreas Schwab
2012-05-01 0:43 ` Junio C Hamano
2012-05-01 7:29 ` Andreas Schwab
2012-05-01 2:51 ` Randal L. Schwartz
2012-05-01 4:27 ` Junio C Hamano
2012-05-01 8:56 ` [PATCH] " Jeff King
2012-05-01 16:12 ` Junio C Hamano
2012-05-01 17:06 ` Junio C Hamano
2012-05-01 20:03 ` 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=4F9F201C.40509@jk.gs \
--to=jk@jk.gs \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=merlyn@stonehenge.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).