All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Øystein Walle" <oystwa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] for-each-ref: add option to omit newlines
Date: Fri, 14 Feb 2014 08:28:38 -0800	[thread overview]
Message-ID: <xmqq38jlk6a1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <loom.20140214T085928-630@post.gmane.org> ("Øystein Walle"'s message of "Fri, 14 Feb 2014 08:11:43 +0000 (UTC)")

Øystein Walle <oystwa@gmail.com> writes:

> However, when specifying a format string it's just a matter of ending
> the format string in '%00' and you're good to go. But then you get the
> null byte *and* a newline. And with your proposal there would be no way
> of saying you want neither.

I very well understand that.  All other commands that support "-z"
to give you NUL terminated output do not consider that a downside.
Why should for-each-ref be special?

  reply	other threads:[~2014-02-14 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 18:00 [PATCH] for-each-ref: add option to omit newlines Øystein Walle
2014-02-13 18:15 ` Øystein Walle
2014-02-13 20:10 ` Junio C Hamano
2014-02-14  8:11   ` Øystein Walle
2014-02-14 16:28     ` Junio C Hamano [this message]
2014-02-14 23:03       ` Øystein Walle
2014-02-14 23:24         ` 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=xmqq38jlk6a1.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=oystwa@gmail.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.