From: Jacob Keller <jacob.keller@gmail.com>
To: Ian Jackson <ijackson@chiark.greenend.org.uk>
Cc: Git mailing list <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 5/6] config docs: Provide for config to specify tags not to abbreviate
Date: Mon, 7 Nov 2016 18:28:17 -0800 [thread overview]
Message-ID: <CA+P7+xoQFsN1tPvKCA6+aRMChFwpMs73D=2kwvVRcxALWK0mZQ@mail.gmail.com> (raw)
In-Reply-To: <20161108005241.19888-6-ijackson@chiark.greenend.org.uk>
On Mon, Nov 7, 2016 at 4:52 PM, Ian Jackson
<ijackson@chiark.greenend.org.uk> wrote:
> +log.noAbbrevTags::
> + Each value is a glob pattern, specifying tag nammes which
> + should always be displayed in full, even when other tags may
> + be omitted or abbreviated (for example, by linkgit:gitk[1]).
> + Values starting with `^` specify tags which should be
> + abbreviated. The order is important: the last match, in the
> + most-local configuration, wins.
> +
It seems weird that this description implies some sort of behavior
change in core git itself, but in fact is only used as a reference for
other tools that may or may not honor it. I guess the reasoning here
is to try to get other external tools that abbreviate tags to also
honor this? But it still seems pretty weird to have a documented
config that has no code in core git to honor it...
Thanks,
Jake
next prev parent reply other threads:[~2016-11-08 2:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 0:52 [PATCH 0/6] Provide for config to specify tags not to abbreviate Ian Jackson
2016-11-08 0:52 ` [PATCH GITK 1/6] gitk: Internal: drawtags: Abolish "singletag" variable Ian Jackson
2016-11-08 0:52 ` [PATCH GITK 2/6] gitk: Internal: drawtags: Idempotently reset "ntags" Ian Jackson
2016-11-08 0:52 ` [PATCH GITK 3/6] gitk: drawtags: Introduce concept of unabbreviated marks Ian Jackson
2016-11-08 0:52 ` [PATCH GITK 4/6] gitk: Provide for config to specify tags not to abbreviate Ian Jackson
2016-11-08 0:52 ` [PATCH 5/6] config docs: " Ian Jackson
2016-11-08 2:28 ` Jacob Keller [this message]
2016-11-08 10:51 ` Ian Jackson
2016-11-08 21:57 ` Jeff King
2016-11-09 1:41 ` Ian Jackson
2016-11-09 5:55 ` Junio C Hamano
2016-11-09 10:51 ` Ian Jackson
2016-11-09 23:13 ` Junio C Hamano
2016-11-09 23:31 ` Ian Jackson
2016-11-10 0:36 ` Markus Hitter
2016-11-08 0:54 ` [PATCH 0/6] " Ian Jackson
2016-11-08 9:19 ` Markus Hitter
2016-11-08 13:42 ` Ian Jackson
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='CA+P7+xoQFsN1tPvKCA6+aRMChFwpMs73D=2kwvVRcxALWK0mZQ@mail.gmail.com' \
--to=jacob.keller@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ijackson@chiark.greenend.org.uk \
/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).