From: Andreas Schwab <schwab@linux-m68k.org>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: git log -z still outputting newlines?
Date: Mon, 30 Apr 2012 20:34:38 +0200 [thread overview]
Message-ID: <m2pqaprrup.fsf@igel.home> (raw)
In-Reply-To: <86ty01qez7.fsf@red.stonehenge.com> (Randal L. Schwartz's message of "Mon, 30 Apr 2012 10:58:04 -0700")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> $ git log -z --format='%cE' -5 | od -c
> 0000000 g i t s t e r @ p o b o x . c o
> 0000020 m \n g i t s t e r @ p o b o x .
> 0000040 c o m \n g i t s t e r @ p o b o
> 0000060 x . c o m \n g i t s t e r @ p o
> 0000100 b o x . c o m \n g i t s t e r @
> 0000120 p o b o x . c o m \n
> 0000132
>
> Why are all those newlines in there? Bug? Misfeature? Feature? If
> feature, how do I ensure \0 in my output? If I add %x00, I get both \0
> *and* \n in output. :(
--format=format:%cE respects the -z option.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-04-30 18:34 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 [this message]
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
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=m2pqaprrup.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.