From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/1] statx04: Remove kernel comments in docparse
Date: Mon, 22 Aug 2022 12:17:25 +0200 [thread overview]
Message-ID: <YwNXtcTF1e5TJdfr@pevik> (raw)
In-Reply-To: <CAEemH2ddjBnyWXt5J-u7qb7DJmQbehVAHXYF50CTWtm74DiFOA@mail.gmail.com>
Hi Li, Xu, all,
> Hi Xu, Petr,
> Petr Vorel <pvorel@suse.cz> wrote:
> > 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.
> We can achieve that but the complexity outweighs the benefits (for LTP).
+1
> > 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:
> That's legacy way in writing comments, but obviously it need unify in format
> for better management in future.
+1 (that was the reason, why I posted it even it's trivial formatting patch, I
should also have posted it as RFC).
> > * 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")
> +1, at most we add this format in normal C comments.
> https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/fanotify/fanotify14.c#L17
> > 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.
> me as well.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-22 10:17 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
2022-08-20 2:03 ` Li Wang
2022-08-22 10:17 ` Petr Vorel [this message]
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=YwNXtcTF1e5TJdfr@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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