From: Julien Grall <julien@xen.org>
To: Anastasiia Lukianenko <Anastasiia_Lukianenko@epam.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"George.Dunlap@citrix.com" <George.Dunlap@citrix.com>
Cc: Artem Mygaiev <Artem_Mygaiev@epam.com>,
"vicooodin@gmail.com" <vicooodin@gmail.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"committers@xenproject.org" <committers@xenproject.org>,
"viktor.mitin.19@gmail.com" <viktor.mitin.19@gmail.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: Xen Coding style and clang-format
Date: Fri, 16 Oct 2020 11:23:45 +0100 [thread overview]
Message-ID: <5bd7cc00-c4c9-0737-897d-e76f22e2fd5b@xen.org> (raw)
In-Reply-To: <4d4f351b152df2c50e18676ccd6ab6b4dc667801.camel@epam.com>
Hi,
On 16/10/2020 10:42, Anastasiia Lukianenko wrote:
> Thanks for your advices, which helped me improve the checker. I
> understand that there are still some disagreements about the
> formatting, but as I said before, the checker cannot be very flexible
> and take into account all the author's ideas.
I am not sure what you refer by "author's ideas" here. The checker
should follow a coding style (Xen or a modified version):
- Anything not following the coding style should be considered as
invalid.
- Anything not written in the coding style should be left
untouched/uncommented by the checker.
> I suggest using the
> checker not as a mandatory check, but as an indication to the author of
> possible formatting errors that he can correct or ignore.
I can understand that short term we would want to make it optional so
either the coding style or the checker can be tuned. But I don't think
this is an ideal situation to be in long term.
The goal of the checker is to automatically verify the coding style and
get it consistent across Xen. If we make it optional or it is
"unreliable", then we lose the two benefits and possibly increase the
contributor frustration as the checker would say A but we need B.
Therefore, we need to make sure the checker and the coding style match.
I don't have any opinions on the approach to achieve that.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-10-16 10:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 9:18 Xen Coding style and clang-format Anastasiia Lukianenko
2020-09-30 9:57 ` Jan Beulich
2020-09-30 10:24 ` George Dunlap
2020-10-01 9:06 ` Anastasiia Lukianenko
2020-10-01 10:06 ` George Dunlap
2020-10-07 10:19 ` Anastasiia Lukianenko
2020-10-08 1:07 ` Stefano Stabellini
2020-10-12 14:37 ` Anastasiia Lukianenko
2020-10-12 18:09 ` George Dunlap
2020-10-13 12:30 ` Jan Beulich
2020-10-16 9:42 ` Anastasiia Lukianenko
2020-10-16 10:23 ` Julien Grall [this message]
2020-10-16 11:37 ` Artem Mygaiev
2020-10-19 18:07 ` Stefano Stabellini
2020-10-20 17:13 ` Julien Grall
2020-10-23 9:39 ` Anastasiia Lukianenko
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=5bd7cc00-c4c9-0737-897d-e76f22e2fd5b@xen.org \
--to=julien@xen.org \
--cc=Anastasiia_Lukianenko@epam.com \
--cc=Artem_Mygaiev@epam.com \
--cc=George.Dunlap@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=committers@xenproject.org \
--cc=jbeulich@suse.com \
--cc=vicooodin@gmail.com \
--cc=viktor.mitin.19@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.