public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Matthieu Moy <Matthieu.Moy@imag•fr>
Cc: git@vger•kernel.org, emma.westby@gmail•com
Subject: Re: [PATCH 4/5] README.md: don't call git stupid in the title
Date: Tue, 23 Feb 2016 11:13:04 -0800	[thread overview]
Message-ID: <xmqqegc31br3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1456249229-30454-5-git-send-email-Matthieu.Moy@imag.fr> (Matthieu Moy's message of "Tue, 23 Feb 2016 18:40:28 +0100")

Matthieu Moy <Matthieu.Moy@imag•fr> writes:

> "the stupid content tracker" was true in the early days of Git, but
> hardly applicable these days. "fast, scalable, distributed" describes
> Git more accuralety.
>
> Also, "stupid" can be seen as offensive by some people. Let's not use it
> in the very first words of the README.
>
> The new formulation is taken from the description of the Debian package.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag•fr>
> ---

This self-derogatory reference shouldn't offend those who didn't
help write it.

Having said that, I agree with the spirit of 4/5 and 5/5; but it is
sad that this line is not resurrected by 5/5 in some way.

>  README.md | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README.md b/README.md
> index 1625352..c11c3e2 100644
> --- a/README.md
> +++ b/README.md
> @@ -1,4 +1,4 @@
> -# Git - the stupid content tracker
> +# Git - fast, scalable, distributed revision control system
>  
>  "git" can mean anything, depending on your mood.

  reply	other threads:[~2016-02-23 19:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 17:40 [RFC/PATCH 0/5] Make README more pleasant to read Matthieu Moy
2016-02-23 17:40 ` [PATCH 1/5] README: use markdown syntax Matthieu Moy
2016-02-23 19:07   ` Junio C Hamano
2016-02-23 19:50     ` Matthieu Moy
2016-02-24  7:08     ` Johannes Schindelin
2016-02-24 10:18       ` Jeff King
2016-02-23 17:40 ` [PATCH 2/5] README.md: add hyperlinks on filenames Matthieu Moy
2016-02-23 19:10   ` Junio C Hamano
2016-02-23 19:52     ` Matthieu Moy
2016-02-23 17:40 ` [PATCH 3/5] README.md: move the link to git-scm.com up Matthieu Moy
2016-02-23 17:40 ` [PATCH 4/5] README.md: don't call git stupid in the title Matthieu Moy
2016-02-23 19:13   ` Junio C Hamano [this message]
2016-02-23 20:51     ` Matthieu Moy
2016-02-23 21:37       ` Junio C Hamano
2016-02-23 17:40 ` [PATCH 5/5] README.md: move down historical explanation about the name Matthieu Moy
2016-02-24 10:22 ` [RFC/PATCH 0/5] Make README more pleasant to read Jeff King
2016-02-24 13:37   ` Matthieu Moy
2016-02-25  6:14     ` Jeff King
2016-02-25  6:22       ` Junio C Hamano
2016-02-25  8:37 ` [PATCH v2 " Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 1/5] README: use markdown syntax Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 2/5] README.md: add hyperlinks on filenames Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 3/5] README.md: move the link to git-scm.com up Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 4/5] README.md: don't call git stupid in the title Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 5/5] README.md: move down historical explanation about the name Matthieu Moy

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=xmqqegc31br3.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=Matthieu.Moy@imag$(echo .)fr \
    --cc=emma.westby@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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