public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
* [LTP] [RFC] linux-git: using whole sha1 hash
@ 2026-03-31  7:20 Petr Vorel
  2026-03-31  7:46 ` Cyril Hrubis
  2026-03-31  8:57 ` Jan Stancek via ltp
  0 siblings, 2 replies; 7+ messages in thread
From: Petr Vorel @ 2026-03-31  7:20 UTC (permalink / raw)
  To: Li Wang, Cyril Hrubis, Andrea Cervesato, Jan Stancek; +Cc: ltp

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [LTP] [RFC] linux-git: using whole sha1 hash
  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
  1 sibling, 2 replies; 7+ messages in thread
From: Cyril Hrubis @ 2026-03-31  7:46 UTC (permalink / raw)
  To: Petr Vorel; +Cc: ltp

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [LTP] [RFC] linux-git: using whole sha1 hash
  2026-03-31  7:46 ` Cyril Hrubis
@ 2026-03-31  8:55   ` Li Wang via ltp
  2026-04-01  9:49   ` Petr Vorel
  1 sibling, 0 replies; 7+ messages in thread
From: Li Wang via ltp @ 2026-03-31  8:55 UTC (permalink / raw)
  To: Cyril Hrubis; +Cc: 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [LTP] [RFC] linux-git: using whole sha1 hash
  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:57 ` Jan Stancek via ltp
  2026-03-31  9:31   ` Petr Vorel
  1 sibling, 1 reply; 7+ messages in thread
From: Jan Stancek via ltp @ 2026-03-31  8:57 UTC (permalink / raw)
  To: Petr Vorel; +Cc: 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [LTP] [RFC] linux-git: using whole sha1 hash
  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
  0 siblings, 1 reply; 7+ messages in thread
From: Petr Vorel @ 2026-03-31  9:31 UTC (permalink / raw)
  To: Jan Stancek; +Cc: 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?

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [LTP] [RFC] linux-git: using whole sha1 hash
  2026-03-31  9:31   ` Petr Vorel
@ 2026-03-31 10:44     ` Jan Stancek via ltp
  0 siblings, 0 replies; 7+ messages in thread
From: Jan Stancek via ltp @ 2026-03-31 10:44 UTC (permalink / raw)
  To: Petr Vorel; +Cc: 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [LTP] [RFC] linux-git: using whole sha1 hash
  2026-03-31  7:46 ` Cyril Hrubis
  2026-03-31  8:55   ` Li Wang via ltp
@ 2026-04-01  9:49   ` Petr Vorel
  1 sibling, 0 replies; 7+ messages in thread
From: Petr Vorel @ 2026-04-01  9:49 UTC (permalink / raw)
  To: Cyril Hrubis; +Cc: ltp

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2026-04-01  9:50 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-03-31 10:44     ` Jan Stancek via ltp

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox