From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clean weird documentation for 'git var' and 'git
Date: Thu, 10 May 2012 19:06:42 +0200 [thread overview]
Message-ID: <4FABF5A2.1050200@lsrfire.ath.cx> (raw)
In-Reply-To: <CAGK7Mr7QWrddaRLkr=1h=GYUNtNVOatQF1sj+p11mejzs65u8A@mail.gmail.com>
Am 10.05.2012 18:45, schrieb Philippe Vaucher:
> Here's a patch removing the weird bits. I spoke about in my previous message.
Ideally, a commit message should be self-contained and explain the
reasons for the introduced changes, or at least contain a link to a
mailing list archive, so that readers who only have the git repository
have a chance to follow the arguments.
>
> Philippe
>
>
> Signed-off-by: Philippe Vaucher<philippe.vaucher@gmail.com>
The author field of a commit plus the sign-off line are enough to
identify you, no extra line with your name required.
> ---
> Documentation/git-commit-tree.txt | 9 ---------
> Documentation/git-var.txt | 9 ---------
> 2 files changed, 18 deletions(-)
>
> diff --git a/Documentation/git-commit-tree.txt
> b/Documentation/git-commit-tree.txt
> index cfb9906..eb8ee99 100644
> --- a/Documentation/git-commit-tree.txt
> +++ b/Documentation/git-commit-tree.txt
> @@ -88,15 +88,6 @@ for one to be entered and terminated with ^D.
>
> include::date-formats.txt[]
>
> -Diagnostics
> ------------
> -You don't exist. Go away!::
> - The passwd(5) gecos field couldn't be read
> -Your parents must have hated you!::
> - The passwd(5) gecos field is longer than a giant static buffer.
> -Your sysadmin must hate you!::
> - The passwd(5) name field is longer than a giant static buffer.
> -
These are actual error messages and their meanings, e.g. git prints "You
don't exist. Go away!" in case the gecos field of your account in
/etc/passwd (or NIS, or LDAP) couldn't be read.
René
prev parent reply other threads:[~2012-05-10 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 16:45 [PATCH] Clean weird documentation for 'git var' and 'git Philippe Vaucher
2012-05-10 16:47 ` Philippe Vaucher
2012-05-10 16:55 ` Junio C Hamano
2012-05-10 18:03 ` Philip Oakley
[not found] ` <CAGK7Mr6AjSY-D9p1vzs=xCg-TMCPiBJDOSxMVYtykeCZCPW2FA@mail.gmail.com>
2012-05-10 18:26 ` Philippe Vaucher
2012-05-10 18:41 ` Junio C Hamano
2012-05-10 20:14 ` Philippe Vaucher
2012-05-10 20:15 ` Philippe Vaucher
2012-05-10 17:06 ` René Scharfe [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=4FABF5A2.1050200@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=philippe.vaucher@gmail.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 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).