From: Jeff King <peff@peff.net>
To: "René Scharfe" <l.s.r@web.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Martin Ågren" <martin.agren@gmail.com>,
"Thomas Rikl" <trikl@online.de>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>
Subject: Re: [Alt. PATCH] ls-remote: deprecate -h as short for --heads
Date: Thu, 19 Oct 2017 16:32:49 -0400 [thread overview]
Message-ID: <20171019203249.76uu3b6ferquitcr@sigill.intra.peff.net> (raw)
In-Reply-To: <26112a15-f02c-a910-c8bb-794ca84dc1e5@web.de>
On Thu, Oct 19, 2017 at 08:26:47PM +0200, René Scharfe wrote:
> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
> index 5f2628c8f8..82622e7fbc 100644
> --- a/Documentation/git-ls-remote.txt
> +++ b/Documentation/git-ls-remote.txt
> @@ -29,6 +29,9 @@ OPTIONS
> These options are _not_ mutually exclusive; when given
> both, references stored in refs/heads and refs/tags are
> displayed.
> ++
> +*NOTE*: -h without any other parameters shows a short help text instead
> +of any refs.
Yuck. This "we only treat -h as special in certain cases" rule is
sufficiently magical that I don't think we want to advertise and lock
ourselves into it.
-Peff
next prev parent reply other threads:[~2017-10-19 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 10:02 Bug: git ls-remote -h / --head results differ in output Thomas Rikl
2017-10-15 11:08 ` Martin Ågren
2017-10-15 13:26 ` René Scharfe
2017-10-17 15:39 ` [PATCH 1/2] git: add NO_INTERNAL_HELP flag for builtins René Scharfe
2017-10-17 17:39 ` Jonathan Nieder
2017-10-17 15:39 ` [PATCH 2/2] ls-remote: use PARSE_OPT_NO_INTERNAL_HELP René Scharfe
2017-10-17 17:42 ` Jonathan Nieder
2017-10-17 17:42 ` Martin Ågren
2017-10-17 15:39 ` [Alt. PATCH] ls-remote: deprecate -h as short for --heads René Scharfe
2017-10-17 17:40 ` Martin Ågren
2017-10-17 17:43 ` Jonathan Nieder
2017-10-17 23:22 ` Junio C Hamano
2017-10-19 18:26 ` René Scharfe
2017-10-19 20:32 ` Jeff King [this message]
2017-10-20 1:04 ` Junio C Hamano
2017-10-20 3:05 ` Jeff King
2017-10-20 5:35 ` Junio C Hamano
2017-10-21 7:16 ` Jeff King
2017-10-21 10:14 ` René Scharfe
2017-10-21 12:18 ` Junio C Hamano
2017-10-23 15:05 ` René Scharfe
2017-10-24 0:52 ` Junio C Hamano
2017-10-24 18:26 ` René Scharfe
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171019203249.76uu3b6ferquitcr@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=l.s.r@web.de \
--cc=martin.agren@gmail.com \
--cc=t.gummerer@gmail.com \
--cc=trikl@online.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).