All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 00/17] Add interpret-trailers builtin
Date: Wed, 29 Jan 2014 20:27:05 +0100 (CET)	[thread overview]
Message-ID: <20140129.202705.1633041266139066645.chriscool@tuxfamily.org> (raw)
In-Reply-To: <xmqqk3dlnnil.fsf@gitster.dls.corp.google.com>

From: Junio C Hamano <gitster@pobox.com>
>
> Is this from the same Christian?

Yes, ...

> The series seems to have unusually high rate of style violations
> compared to the usual submission, like these:
> 
> ERROR: open brace '{' following function declarations go on the next line
> #78: FILE: trailer.c:44:
> +static size_t alnum_len(const char *buf, size_t len) {
> 
> ERROR: trailing statements should be on next line
> #79: FILE: trailer.c:45:
> +	while (--len >= 0 && !isalnum(buf[len]));
> 
> ERROR: space required before the open parenthesis '('
> #70: FILE: trailer.c:90:
> +	switch(arg_tok->conf->if_exist) {
> 
> WARNING: braces {} are not necessary for any arm of this statement
> #66: FILE: trailer.c:270:
> +	if (!strcasecmp("doNothing", value)) {
> [...]
> +	} else if (!strcasecmp("add", value)) {
> [...]
> +	} else
> [...]
> 
> ERROR: that open brace { should be on the previous line
> #96: FILE: trailer.c:300:
> +	for (previous = NULL, item = first_conf_item;
> +	     item;
> +	     previous = item, item = item->next)
> +	{
> 
> Just trying to see if there is an impersonation ;-)

... I guess the artistic part of my mind is trying to come out somehow.

Thanks,
Christian.

      reply	other threads:[~2014-01-29 19:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 16:59 [PATCH v3 00/17] Add interpret-trailers builtin Christian Couder
2014-01-26 16:59 ` [PATCH v3 01/17] Add data structures and basic functions for commit trailers Christian Couder
2014-01-26 16:59 ` [PATCH v3 02/17] trailer: process trailers from file and arguments Christian Couder
2014-01-26 16:59 ` [PATCH v3 03/17] trailer: read and process config information Christian Couder
2014-01-26 16:59 ` [PATCH v3 04/17] trailer: process command line trailer arguments Christian Couder
2014-01-26 16:59 ` [PATCH v3 05/17] strbuf: add strbuf_isspace() Christian Couder
2014-01-26 16:59 ` [PATCH v3 06/17] trailer: parse trailers from input file Christian Couder
2014-01-26 17:00 ` [PATCH v3 07/17] trailer: put all the processing together and print Christian Couder
2014-01-26 17:00 ` [PATCH v3 08/17] trailer: add interpret-trailers command Christian Couder
2014-01-26 17:00 ` [PATCH v3 09/17] trailer: add tests for "git interpret-trailers" Christian Couder
2014-01-26 17:00 ` [PATCH v3 10/17] trailer: if no input file is passed, read from stdin Christian Couder
2014-01-26 17:00 ` [PATCH v3 11/17] trailer: add new_trailer_item() function Christian Couder
2014-01-26 17:00 ` [PATCH v3 12/17] strbuf: add strbuf_replace() Christian Couder
2014-01-26 17:00 ` [PATCH v3 13/17] trailer: execute command from 'trailer.<name>.command' Christian Couder
2014-01-26 17:00 ` [PATCH v3 14/17] trailer: add tests for trailer command Christian Couder
2014-01-26 17:00 ` [PATCH v3 15/17] trailer: set author and committer env variables Christian Couder
2014-01-26 17:00 ` [PATCH v3 16/17] trailer: add tests for commands using " Christian Couder
2014-01-26 17:00 ` [PATCH v3 17/17] Documentation: add documentation for 'git interpret-trailers' Christian Couder
2014-01-27  0:52   ` Eric Sunshine
2014-01-27 20:33     ` Christian Couder
2014-01-27 21:20       ` Junio C Hamano
2014-01-29 20:01         ` Christian Couder
2014-01-29 20:30           ` Junio C Hamano
2014-02-02 11:22       ` Eric Sunshine
2014-01-27 21:05 ` [PATCH v3 00/17] Add interpret-trailers builtin Junio C Hamano
2014-01-29 19:27   ` Christian Couder [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=20140129.202705.1633041266139066645.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.