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

Re: [PATCH v2 1/1] config: learn the --stdin option for instructions

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jan 28, 2020, 13:42 UTC
Message-ID
<CAPig+cQJeT-pU-cUE4YEKcb4P_0X2sB1srGMCiOfyt6DZEcbgg@mail.gmail.com>
In-Reply-To
<20200128092414.GB574544@coredump.intra.peff.net>
On Tue, Jan 28, 2020 at 4:24 AM Jeff King <peff@peff.net> wrote:
Show 8 quoted lines
> On Mon, Jan 27, 2020 at 11:59:03AM -0500, Eric Sunshine wrote:
> >     set SP <key> SP <value> NUL
> >     unset SP <key> LF
>
> The section and key parts of a config key are pretty restricted, but the
> subsection portion can contain anything except newline and NUL. So in
> particular, it would be valid to have a space, which would make the
> input ambiguous.

I was wondering if that might be the case (particularly, if space was allowed). Thanks for the education.

Previous: Jeff KingNext: Junio C Hamano
Message 6 of 9 in “config: read instructions from stdin”
  1. 0/1 config: read instructions from stdinZeger-Jan van de Weg, Jan 27, 2020
  2. 1/1 config: learn the --stdin option for instructionsZeger-Jan van de Weg, Jan 27, 2020
  3. Christian CouderJan 27, 2020
  4. Eric SunshineJan 27, 2020
  5. Jeff KingJan 28, 2020
  6. Eric SunshineJan 28, 2020
  7. Junio C HamanoJan 28, 2020
  8. Jeff KingJan 29, 2020
  9. Jeff KingJan 28, 2020

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.