From: Johannes Sixt <j6t@kdbg.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH v2] Remove --allow-empty from the git-commit synopsis
Date: Wed, 7 Apr 2010 20:55:29 +0200 [thread overview]
Message-ID: <201004072055.30017.j6t@kdbg.org> (raw)
In-Reply-To: <1270661327-28078-1-git-send-email-avarab@gmail.com>
On Mittwoch, 7. April 2010, Ævar Arnfjörð Bjarmason wrote:
> --- a/Documentation/git-commit.txt
> +++ b/Documentation/git-commit.txt
> @@ -10,9 +10,8 @@ SYNOPSIS
> [verse]
> 'git commit' [-a | --interactive] [-s] [-v] [-u<mode>] [--amend]
> [--dry-run] [(-c | -C) <commit>] [-F <file> | -m <msg>] [--reset-author]
> - [--allow-empty] [--no-verify] [-e] [--author=<author>]
> - [--date=<date>] [--cleanup=<mode>] [--status | --no-status] [--]
> - [[-i | -o ]<file>...]
> + [--no-verify] [-e] [--author=<author>] [--date=<date>]
> + [--cleanup=<mode>] [--status | --no-status] [--] [[-i | -o ]<file>...]
IMO the option should not be removed from the synopsis section of the
documentation. I would agree that it is removed from the output of 'git
commit -h', and I think this was the original intent when someone (Junio?)
suggested to remove it.
-- Hannes
next prev parent reply other threads:[~2010-04-07 18:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 22:06 Does Git really need a commit message to go with a commit? Ævar Arnfjörð Bjarmason
2010-04-04 1:58 ` Avery Pennarun
[not found] ` <p2kadf1fd3d1004031526r3beff4e3ldd977dfc7e9da782@mail.gmail.com>
[not found] ` <h2m51dd1af81004040415xc7381f6cp1bf81bcfd684b99d@mail.gmail.com>
2010-04-04 12:37 ` Santi Béjar
2010-04-04 14:49 ` [PATCH] Add option to git-commit to allow empty log messages Ævar Arnfjörð Bjarmason
2010-04-04 22:43 ` David Aguilar
2010-04-04 23:53 ` Ævar Arnfjörð Bjarmason
2010-04-05 2:11 ` Junio C Hamano
2010-04-05 2:15 ` Sverre Rabbelier
2010-04-05 3:57 ` Junio C Hamano
2010-04-05 14:46 ` Sverre Rabbelier
2010-04-05 5:10 ` Miles Bader
2010-04-05 5:27 ` Junio C Hamano
2010-04-05 5:51 ` Jeff King
2010-04-05 12:50 ` Ævar Arnfjörð Bjarmason
2010-04-05 17:58 ` Jonathan Nieder
2010-04-05 18:11 ` Jonathan Nieder
2010-04-06 5:55 ` Jeff King
2010-04-06 8:40 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2010-04-07 5:16 ` Junio C Hamano
2010-04-07 14:28 ` Ævar Arnfjörð Bjarmason
2010-04-06 8:42 ` [PATCH] " Ævar Arnfjörð Bjarmason
2010-04-07 15:09 ` [PATCH] Remove --allow-empty from the git-commit synopsis Ævar Arnfjörð Bjarmason
2010-04-07 15:29 ` Sverre Rabbelier
2010-04-07 17:28 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2010-04-07 17:52 ` Sverre Rabbelier
2010-04-07 18:17 ` Ævar Arnfjörð Bjarmason
2010-04-07 18:21 ` Tay Ray Chuan
2010-04-07 18:48 ` [PATCH v3] " Ævar Arnfjörð Bjarmason
2010-04-07 18:55 ` Johannes Sixt [this message]
2010-04-07 19:00 ` [PATCH v2] " Junio C Hamano
2010-04-07 19:28 ` [PATCH v4] " Ævar Arnfjörð Bjarmason
2010-04-07 19:45 ` Stephen Boyd
2010-04-07 22:25 ` [PATCH v2] " Junio C Hamano
2010-04-08 6:44 ` Jeff King
2010-04-06 5:43 ` [PATCH] Add option to git-commit to allow empty log messages Jeff King
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=201004072055.30017.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=avarab@gmail.com \
--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 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).