git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: Zeger-Jan van de Weg <git@zjvandeweg.nl>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] config: learn the --stdin option for instructions
Date: Tue, 28 Jan 2020 08:42:21 -0500	[thread overview]
Message-ID: <CAPig+cQJeT-pU-cUE4YEKcb4P_0X2sB1srGMCiOfyt6DZEcbgg@mail.gmail.com> (raw)
In-Reply-To: <20200128092414.GB574544@coredump.intra.peff.net>

On Tue, Jan 28, 2020 at 4:24 AM Jeff King <peff@peff.net> wrote:
> 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.

  reply	other threads:[~2020-01-28 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 10:09 [PATCH v2 0/1] config: read instructions from stdin Zeger-Jan van de Weg
2020-01-27 10:09 ` [PATCH v2 1/1] config: learn the --stdin option for instructions Zeger-Jan van de Weg
2020-01-27 11:44   ` Christian Couder
2020-01-27 16:59   ` Eric Sunshine
2020-01-28  9:24     ` Jeff King
2020-01-28 13:42       ` Eric Sunshine [this message]
2020-01-28 19:28       ` Junio C Hamano
2020-01-29  2:37         ` Jeff King
2020-01-28  9:19   ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPig+cQJeT-pU-cUE4YEKcb4P_0X2sB1srGMCiOfyt6DZEcbgg@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=git@zjvandeweg.nl \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).