git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Vincent van Ravesteijn <vfr@lyx.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 1/2] Unification of user message strings
Date: Mon, 19 Mar 2012 16:53:00 -0400	[thread overview]
Message-ID: <20120319205300.GA3039@sigill.intra.peff.net> (raw)
In-Reply-To: <1332179503-2992-2-git-send-email-vfr@lyx.org>

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:

  $ git grep -E '(error|die)\((_\()?"[A-Z]' | wc -l
  810
  $ git grep -E '(error|die)\((_\()?"[a-z]' | wc -l
  1267

-Peff

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.

   The first number is the percentage of an author's messages starting
   with upper-case characters, followed by the total number of messages
   for that author, followed by the author's name. I limited the output
   to the top 20 by total number, as there is a long tail of people
   contributing just a few messages.

      0.14 37 Martin Koegler
      0.14 42 Johannes Sixt
      0.14 81 Jonathan Nieder
      0.16 31 Pierre Habouzit
      0.18 92 Nicolas Pitre
      0.20 66 Jeff King
      0.20 87 Linus Torvalds
      0.26 348 Junio C Hamano
      0.35 20 Christian Couder
      0.37 43 Nguyễn Thái Ngọc Duy
      0.39 18 René Scharfe
      0.41 32 Miklos Vajna
      0.45 270 Ævar Arnfjörð Bjarmason
      0.47 129 Shawn O. Pearce
      0.50 36 David Barr
      0.54 57 Johannes Schindelin
      0.62 39 Ramkumar Ramachandra
      0.67 21 Daniel Barkalow
      0.76 59 Johan Herland

   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:".

  parent reply	other threads:[~2012-03-19 20:53 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 [this message]
2012-03-19 21:36     ` Junio C Hamano
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=20120319205300.GA3039@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).