git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Vincent van Ravesteijn <vfr@lyx.org>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Unification of user message strings
Date: Mon, 19 Mar 2012 14:36:29 -0700	[thread overview]
Message-ID: <7vaa3c9ste.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120319205300.GA3039@sigill.intra.peff.net> (Jeff King's message of "Mon, 19 Mar 2012 16:53:00 -0400")

Jeff King <peff@peff.net> writes:

> On Mon, Mar 19, 2012 at 06:51:42PM +0100, Vincent van Ravesteijn wrote:
>
>> Rewrite user messages to stick to a uniform style for all messages.
>> From the surrounding code, the following guidelines were deduced:
>> - messages start with a capital,
>
> I was surprised by this one, as I think we generally use lower-case
> messages. Grepping shows that lower-case has a slight edge, though it is
> far from decided:
> ...
> PS I was curious if it was simply that some people prefer one way and
>    not the other, but the results are quite mixed. Below is the result
>    of a small script I wrote that calculates "upper-casedness" per
>    author using the above regexes and git-blame.
> ...
>    You can see that some people are usually lowercase and some are usually
>    uppercase, but there are many people near 50%, doing both equally.
>    There's also some inaccuracy in my simplistic sampling. For example,
>    of my 13 upper-case messages, 11 of them are "BUG:".

I had a vague impression that plumbing messages tend to be lowercase.  If
it is not be too much trouble, it might be interesting to redo the numbers
divided into the plumbing and Porcelain messages. Perhaps these "50%"
folks updated both plumbing and Porcelain. Another possibility is that
they tried to follow the local convention when they added a new one, or
reworded an existing one.

If we would be rewording, we would only be doing the Porcelain messages,
so I am OK with either way.

  reply	other threads:[~2012-03-19 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 17:51 [PATCH 0/2] Unify the style of user messages Vincent van Ravesteijn
2012-03-19 17:51 ` [PATCH 1/2] Unification of user message strings Vincent van Ravesteijn
2012-03-19 19:39   ` Junio C Hamano
2012-03-19 20:16     ` Vincent van Ravesteijn
2012-03-19 20:53   ` Jeff King
2012-03-19 21:36     ` Junio C Hamano [this message]
2012-03-20  7:47       ` Vincent van Ravesteijn
2012-03-20 12:01         ` Jakub Narebski
2012-03-20 12:33           ` Vincent van Ravesteijn
2012-03-19 17:51 ` [PATCH 2/2] Make some strings translatable Vincent van Ravesteijn

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=7vaa3c9ste.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=vfr@lyx.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.
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).