git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
	git@vger.kernel.org, Johan Herland <johan@herland.net>,
	Thomas Rast <tr@thomasrast.ch>,
	Michael Haggerty <mhagger@alum.mit.edu>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Greg Kroah-Hartman <greg@kroah.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
Date: Mon, 30 Dec 2013 14:27:19 -0800	[thread overview]
Message-ID: <20131230222719.GN6840@leaf> (raw)
In-Reply-To: <xmqqfvpaqcbu.fsf@gitster.dls.corp.google.com>

On Mon, Dec 30, 2013 at 01:05:25PM -0800, Junio C Hamano wrote:
> Josh Triplett <josh@joshtriplett.org> writes:
> >>  - With your scheme, if you already had _one_ trailing SPs in the
> >>    input, it would be hard to spot in the source;
> >
> > Git makes them quite difficult to miss. :)
> 
> That is irrelevant, isn't it?
> 
> This is about protecting the source in the editor, before you run
> "git show --whitespace=trailing-space", "git diff --check", etc.

That was exactly my point: such lines shouldn't exist, and rather than
including the trailing space and following it with a character that then
needs removing, it seems more sensible to me to omit the trailing space
and insert it via an almost identical sed line.  Git already helps
ensure that trailing space won't exist on *any* line, including those; I
don't see how an extra character after the space (making it no longer
trailing space) makes it any more or less likely that those lines would
have trailing space.

In any case, I don't care enough to argue the point further; it was just
a style suggestion.

- Josh Triplett

      reply	other threads:[~2013-12-30 22:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  6:37 [PATCH 0/9] Add interpret-trailers builtin Christian Couder
2013-12-24  6:37 ` [PATCH 1/9] Add data structures and basic functions for commit trailers Christian Couder
2013-12-24  6:37 ` [PATCH 2/9] trailer: process trailers from file and arguments Christian Couder
2013-12-24  6:37 ` [PATCH 3/9] trailer: read and process config information Christian Couder
2013-12-24 13:47   ` Christian Couder
2013-12-24  6:37 ` [PATCH 4/9] trailer: process command line trailer arguments Christian Couder
2013-12-24  6:37 ` [PATCH 5/9] strbuf: add strbuf_isspace() Christian Couder
2013-12-24  6:37 ` [PATCH 6/9] trailer: parse trailers from input file Christian Couder
2013-12-24  6:37 ` [PATCH 7/9] trailer: put all the processing together and print Christian Couder
2013-12-24  6:37 ` [PATCH 8/9] trailer: add interpret-trailers command Christian Couder
2013-12-24  6:37 ` [PATCH 9/9] trailer: add tests for "git interpret-trailers" Christian Couder
2013-12-30 17:19   ` Junio C Hamano
2013-12-30 20:20     ` Josh Triplett
2013-12-30 20:46       ` Junio C Hamano
2013-12-30 20:52         ` Josh Triplett
2013-12-30 21:05           ` Junio C Hamano
2013-12-30 22:27             ` Josh Triplett [this message]

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=20131230222719.GN6840@leaf \
    --to=josh@joshtriplett.org \
    --cc=chriscool@tuxfamily.org \
    --cc=dan.carpenter@oracle.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=greg@kroah.com \
    --cc=johan@herland.net \
    --cc=mhagger@alum.mit.edu \
    --cc=peff@peff.net \
    --cc=tr@thomasrast.ch \
    /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 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 NNTP newsgroup(s).