[LTP] [RFC] linux-git: using whole sha1 hash

[LTP] [RFC] linux-git: using whole sha1 hash

[Petr Vorel]

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).

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

Re: [LTP] [RFC] linux-git: using whole sha1 hash

[Cyril Hrubis]

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

Re: [LTP] [RFC] linux-git: using whole sha1 hash

[Li Wang via ltp]

On Tue, Mar 31, 2026 at 3:46 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
> 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.

+1

-- 
Regards,
Li Wang


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] [RFC] linux-git: using whole sha1 hash

[Petr Vorel]

Hi all,

> 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.

Thanks all to ack (or at least no objection), I'll add the above to my TODO
list, hope to get to it in reasonable time.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] [RFC] linux-git: using whole sha1 hash

[Jan Stancek via ltp]

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?

>
> 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

Re: [LTP] [RFC] linux-git: using whole sha1 hash

[Petr Vorel]

> 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

Re: [LTP] [RFC] linux-git: using whole sha1 hash

[Jan Stancek via ltp]

On Tue, Mar 31, 2026 at 11:31 AM Petr Vorel <pvorel@suse.cz> wrote:
>
> > 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.

No objections.

>
> 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