git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] for-each-ref: add option to omit newlines

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 14, 2014, 16:28 UTC
Message-ID
<xmqq38jlk6a1.fsf@gitster.dls.corp.google.com>
In-Reply-To
<loom.20140214T085928-630@post.gmane.org>
Ø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?

Previous: Øystein WalleNext: Øystein Walle
Message 5 of 7 in “for-each-ref: add option to omit newlines”
  1. for-each-ref: add option to omit newlinesØystein Walle, Feb 13, 2014
  2. Øystein WalleFeb 13, 2014
  3. Junio C HamanoFeb 13, 2014
  4. Øystein WalleFeb 14, 2014
  5. Junio C HamanoFeb 14, 2014
  6. Øystein WalleFeb 14, 2014
  7. Junio C HamanoFeb 14, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.