From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC] linux-git: using whole sha1 hash
Date: Tue, 31 Mar 2026 09:46:28 +0200 [thread overview]
Message-ID: <act71G89AKEf63LA@yuki.lan> (raw)
In-Reply-To: <20260331072051.GA5254@pevik>
Hi!
> 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).
Sounds good to me.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-31 7:46 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 [this message]
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
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=act71G89AKEf63LA@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.