git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: William Hubbs <williamh@gentoo.org>,
	git@vger.kernel.org, chutzpah@gentoo.org
Subject: Re: [PATCH v3 1/1] config: allow giving separate author and committer idents
Date: Mon, 04 Feb 2019 10:57:04 -0800	[thread overview]
Message-ID: <xmqqbm3rv0u7.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1902041314160.41@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 4 Feb 2019 13:17:35 +0100 (STD)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> I do not recall we crossed the bridge to allow trailing comma here
>> at the end of enum definition.
>
> In advice.c:
>
> 	enum color_advice {
> 		ADVICE_COLOR_RESET = 0,
> 		ADVICE_COLOR_HINT = 1,
> 	};
>
> In builtin/pack-objects.c:
>
> 	enum missing_action {
> 		MA_ERROR = 0,      /* fail if any missing objects are encountered */
> 		MA_ALLOW_ANY,      /* silently allow ALL missing objects */
> 		MA_ALLOW_PROMISOR, /* silently allow all missing PROMISOR objects */
> 	};
>
> In builtin/rev-list.c:
>
> 	enum missing_action {
> 		MA_ERROR = 0,    /* fail if any missing objects are encountered */
> 		MA_ALLOW_ANY,    /* silently allow ALL missing objects */
> 		MA_PRINT,        /* print ALL missing objects in special section */
> 		MA_ALLOW_PROMISOR, /* silently allow all missing PROMISOR objects */
> 	};
>
> ... and I will stop here. You are correct that the majority of our enums
> does not let its last item end in a comma. But we did cross that bridge.

Good.  Thanks for eyeballing.

I do not think any of these can be compiled out on a platform with a
picker compiler, and the one in rev-list.c is from late 2017, so it
probably be a safe assumption that nobody would mind the trailing
comma.


      reply	other threads:[~2019-02-04 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 23:08 [PATCH v3 0/1] config: allow giving different author and committer idents William Hubbs
2019-01-29 23:08 ` [PATCH v3 1/1] config: allow giving separate " William Hubbs
2019-01-29 23:33   ` Junio C Hamano
2019-02-04 12:17     ` Johannes Schindelin
2019-02-04 18:57       ` Junio C Hamano [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

  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=xmqqbm3rv0u7.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chutzpah@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=williamh@gentoo.org \
    /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).