All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	git@vger.kernel.org,  git@jowil.de
Subject: Re: [PATCH 3/4] t5604: do not expect that HEAD is a valid tagname
Date: Tue, 03 Dec 2024 10:29:14 +0900	[thread overview]
Message-ID: <xmqq34j5h7v9.fsf@gitster.g> (raw)
In-Reply-To: <20241202210006.GE776185@coredump.intra.peff.net> (Jeff King's message of "Mon, 2 Dec 2024 16:00:06 -0500")

Jeff King <peff@peff.net> writes:

> So I'd expect 10 digits in a fresh clone of git.git. It's possible Junio
> has set core.abbrev to something fixed, though.

Thanks.

I have "git one" (and "git who") aliased to this script:

    $ cat $(type --path git-onewho)
    #!/bin/sh
    if sha1=$(git rev-parse -q --verify "$1")
    then
            git show --date=short -s --abbrev=8 --pretty='format:%h (%s, %ad)' "$1"
    else
            git log -1 --format="%aN <%aE>" --author="$1" --all
    fi | tr -d "\012"
    $ git help one
    'one' is aliased to 'onewho'
    $ git help who
    'who' is aliased to 'onewho'
    
so that I can say "\C-u ESC ! git one HEAD" (or "git one peff")
while writing a piece of e-mail.  I can drop --abbrev=8 from there
but the machinery knows to bust that limit if it is necessary to
ensure uniqueness, so ...

  parent reply	other threads:[~2024-12-03  1:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02  7:07 [PATCH 0/4] forbid HEAD as a tagname Junio C Hamano
2024-12-02  7:07 ` [PATCH 1/4] refs: move ref name helpers around Junio C Hamano
2024-12-02 20:37   ` Jeff King
2024-12-03  1:23     ` Junio C Hamano
2024-12-02  7:07 ` [PATCH 2/4] refs: drop strbuf_ prefix from helpers Junio C Hamano
2024-12-02 20:51   ` Jeff King
2024-12-02  7:07 ` [PATCH 3/4] t5604: do not expect that HEAD is a valid tagname Junio C Hamano
2024-12-02 12:19   ` Kristoffer Haugsbakk
2024-12-02 21:00     ` Jeff King
2024-12-02 21:09       ` Kristoffer Haugsbakk
2024-12-03  1:29       ` Junio C Hamano [this message]
2024-12-05 20:25         ` Jeff King
2024-12-02 20:52   ` Jeff King
2024-12-02  7:07 ` [PATCH 4/4] tag: "git tag" refuses to use HEAD as a tagname Junio C Hamano
2024-12-02 10:54   ` Patrick Steinhardt
2024-12-02 13:01   ` shejialuo
2024-12-03  1:30     ` Junio C Hamano
2024-12-05 20:26       ` Jeff King
2024-12-05 20:27         ` Jeff King
2024-12-02 20:42   ` Rubén Justo
2024-12-03  1:35     ` Junio C Hamano
2024-12-02 21:03   ` 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=xmqq34j5h7v9.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@jowil.de \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.