From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC] linux-git: using whole sha1 hash
Date: Tue, 31 Mar 2026 11:31:10 +0200 [thread overview]
Message-ID: <20260331093110.GA37783@pevik> (raw)
In-Reply-To: <CAASaF6xPzR3KWCd=aUTPWVgzfyi1SkftgQ8HG_kvphY2fWMe_g@mail.gmail.com>
> On Tue, Mar 31, 2026 at 9:21 AM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi all,
> > anything against starting to use whole sha1 hash in linux-git tag? i.e. 40 chars.
> > It can be shorten by the doc/conf.py script (use whole hash for URL, but shorten
> > the visible part of <a> tag).
> In metdata, commit messages or everywhere?
In metadata.
Instead of:
.tags = (const struct tst_tag[]) {
{"linux-git", "091d0d55b286"},
...
Have:
.tags = (const struct tst_tag[]) {
{"linux-git", "091d0d55b286c9340201b4ed4470be87fc568228"},
Kind regards,
Petr
> > We normally use only 12 chars 091d0d55b286, but some users during rewrite used
> > [1] really small hash (7 chars) from original test.
> > Kind regards,
> > Petr
> > [1] https://lore.kernel.org/ltp/20260331015538.53326-1-lufei@uniontech.com/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-31 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 7:20 [LTP] [RFC] linux-git: using whole sha1 hash Petr Vorel
2026-03-31 7:46 ` Cyril Hrubis
2026-03-31 8:55 ` Li Wang via ltp
2026-04-01 9:49 ` Petr Vorel
2026-03-31 8:57 ` Jan Stancek via ltp
2026-03-31 9:31 ` Petr Vorel [this message]
2026-03-31 10:44 ` Jan Stancek via ltp
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=20260331093110.GA37783@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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