linux-git: using whole sha1 hash
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/[email protected]/
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Hi!
Quoted 3 lines
anything against starting to use whole sha1 hash in linux-git tag? i.e. 40 chars. It can be shorten by the
doc/conf.pyscript (use whole hash for URL, but shorten the visible part of <a> tag).
Sounds good to me.
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 7 lines · Cyril Hrubis
Hi!
Quoted 3 lines
anything against starting to use whole sha1 hash in linux-git tag? i.e. 40 chars. It can be shorten by the
doc/conf.pyscript (use whole hash for URL, but shorten the visible part of <a> tag).Sounds good to me.
+1
Signature · 6 lines
Regards, Li Wang -- Mailing list info: https://lists.linux.it/listinfo/ltp
Hi all,
Quoted 6 lines
Hi!
Quoted 3 lines
anything against starting to use whole sha1 hash in linux-git tag? i.e. 40 chars. It can be shorten by the
doc/conf.pyscript (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
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 6 lines · 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.pyscript (use whole hash for URL, but shorten the visible part of <a> tag).
In metdata, commit messages or everywhere?
Quoted 9 lines
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
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 9 lines · Petr Vorel
Quoted 6 lines
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.pyscript (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
Quoted 7 lines
Quoted 7 lines
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
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Quoted 5 lines · Petr Vorel
Quoted 4 lines · Petr Vorel
Quoted 2 lines
Hi all,
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
anything against starting to use whole sha1 hash in linux-git tag? i.e. 40 chars. It can be shorten by the
doc/conf.pyscript (use whole hash for URL, but shorten the visible part of <a> tag).In metdata, commit messages or everywhere?
In metadata.
No objections.
Quoted 22 lines
Instead of:
.tags = (const struct tst_tag[]) { {"linux-git", "091d0d55b286"}, ...Have:
.tags = (const struct tst_tag[]) { {"linux-git", "091d0d55b286c9340201b4ed4470be87fc568228"},Kind regards,
PetrQuoted 7 lines
Quoted 7 lines
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
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp