From: Petr Vorel <pvorel@suse.cz>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/1] statx04: Remove kernel comments in docparse
Date: Fri, 19 Aug 2022 16:32:37 +0200 [thread overview]
Message-ID: <Yv+fBabMjCy3CLlo@pevik> (raw)
In-Reply-To: <75b595dd-fdcb-73db-0e71-d36d665bbad8@fujitsu.com>
Hi all,
thanks all for their input.
> Hi Li
> > So for me, If remove kernel commit in description, then I only see
> > useless commit id number, unless I go to search them in kernel org.
> > Not exactly, another thing to make people's attention is test fail with
> > hint,
> > then we can simply click the link.
> I remember Amir also added a similar feature[1] to xfstests when he
> become xfs 5.10 stable kernel maintainer.
> So maybe we can add a third colume in tst_test struct's tag field to
> cover kernel commit title? Then this kernel comment can be removed.
Amir got inspiration from LTP, but I'm not a big fan of adding manually git
subject which is now added by script. Also I'd like to address the change we
agree also in fanotify sources.
> Also, I don't have strong obejection to this patch because it seems
> duplicate, but I just want to keep kernel commit title by using simple way.
I also wonder why people add commits in this verbose form:
* commit 93bc420ed41df63a18ae794101f7cbf45226a6ef
* Author: yangerkun <yangerkun@huawei.com>
* Date: Mon Feb 18 09:07:02 2019 +0800
*
* ext2: support statx syscall
If commits are really necessary I'd add them inline, i.e.:
$ git log --pretty=format:'%h ("%s")' -1 93bc420ed41d
93bc420ed41d ("ext2: support statx syscall")
But again, having git hash at the bottom and then full commit on the top looks
to me just a redundancy (I often want to see changes in kernel thus run git show
hash anyway + there is that link in docparse.
So let's wait for opinion of other people.
Kind regards,
Petr
> [1]https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/?id=4fb72cffd9e3251149d9fa25daa96b2e26b62eab
> Best Regards
> Yang Xu
> > 58 HINT: You _MAY_ be missing kernel fixes:
> > 59
> > 60 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=93bc420ed41d <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=93bc420ed41d>
> > 61 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=99652ea56a41 <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=99652ea56a41>
> > 62 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=04a87e347282 <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=04a87e347282>
> > 63https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f955f26f3d4 <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f955f26f3d4>
> > --
> > Regards,
> > Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-19 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 9:07 [LTP] [PATCH 1/1] statx04: Remove kernel comments in docparse Petr Vorel
2022-08-19 10:02 ` xuyang2018.jy
2022-08-19 10:10 ` xuyang2018.jy
2022-08-19 11:22 ` Petr Vorel
2022-08-19 12:42 ` Li Wang
2022-08-19 12:55 ` Li Wang
2022-08-19 14:10 ` xuyang2018.jy
2022-08-19 14:32 ` Petr Vorel [this message]
2022-08-20 2:03 ` Li Wang
2022-08-22 10:17 ` Petr Vorel
2022-08-19 12:36 ` Li Wang
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=Yv+fBabMjCy3CLlo@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).