From: Ishani <chugh.ishani@research.iiit.ac.in>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
cardoe <cardoe@cardoe.com>, Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [Outreachy] Interested in contribution: Code Standards Checking using clang-format
Date: Mon, 17 Apr 2017 01:30:59 +0530 (IST) [thread overview]
Message-ID: <1130763396.5603480.1492372859631.JavaMail.zimbra@research.iiit.ac.in> (raw)
In-Reply-To: <99C935C0-DD6F-475E-B026-D6ADF871DCE4@gmail.com>
Hello,
Please review the following file for Xen Hypervisor format specification given in http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=CODING_STYLE
The link to the file is:
https://github.com/sam5125/Xen-Clang-format/blob/master/Supported/correct.c
Regards,
Ishani
----- Original Message -----
From: "Lars Kurth" <lars.kurth.xen@gmail.com>
To: "Ishani" <chugh.ishani@research.iiit.ac.in>
Cc: "cardoe" <cardoe@cardoe.com>, "xen-devel" <xen-devel@lists.xenproject.org>, "Andrew Cooper" <andrew.cooper3@citrix.com>, "Wei Liu" <wei.liu2@citrix.com>
Sent: Tuesday, April 11, 2017 5:22:02 PM
Subject: Re: [Xen-devel] [Outreachy] Interested in contribution: Code Standards Checking using clang-format
Ishani,
> On 11 Apr 2017, at 12:21, Ishani <chugh.ishani@research.iiit.ac.in> wrote:
>
> Hello,
>
> I have created a clang-format file for specifications of format for Xen hypervisor and incorporated all of the support which present clang-format could provide. I have seen all the options provided by clang-format and have some discrepancies regarding some of format specifications which are not provided in the doc but is followed. I will commit the code and provide you with full report by today.
Can you post this on any public repo for now (e.g. github gitlab bitbucket, whatever) and post an e-mail on this list with title "[RFC] Code Standards Checking using clang-format" or something like it with link to the repo. I think this is enough for the small task required for this project.
Ideally, because at some point you will need to do this, you would follow https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches - but we could waive this in this case. But it will make reviewing the output easier.
>> 4: a small script that checks that .clang-format works correctly on these pieces of code
>
>> For 4, you probably want to run clang-format with -output-replacements-xml on the files in 1 >- 3 and then do some grep magic to see whether it does the right thing.
>
> Can you elaborate on this a bit. What is the expected end product?
I think this is a stretch goal, given the time-frame. The idea here was to be able to verify that the clang-format file works as expected on some code snippets that we know adhere to the coding standards. This would in essence produce a stand-alone test for the .clang-format file on the coding style patterns that we know works.
> Meanwhile, I have resumed on writing the proposal. I somehow missed previous comments. Please have a look at it.
> https://docs.google.com/document/d/10NJn-QvO1TvyJJJGE2PD6FtElYCT3neBAffIqeWHdiE/edit?usp=sharing
I saw it. Thank you!
Best Regards
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-16 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 9:37 [Outreachy] Interested in contribution: Code Standards Checking using clang-format Ishani
2017-04-03 11:00 ` Lars Kurth
2017-04-03 12:01 ` Ishani
2017-04-03 16:22 ` Lars Kurth
2017-04-11 11:21 ` Ishani
2017-04-11 11:52 ` Lars Kurth
2017-04-16 20:00 ` Ishani [this message]
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=1130763396.5603480.1492372859631.JavaMail.zimbra@research.iiit.ac.in \
--to=chugh.ishani@research.iiit.ac.in \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=lars.kurth.xen@gmail.com \
--cc=wei.liu2@citrix.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 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).