From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "Luca Fancellu" <Luca.Fancellu@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Bertrand Marquis" <Bertrand.Marquis@arm.com>,
"Oleksandr Andrushchenko" <andr2000@gmail.com>,
xen-devel@lists.xenproject.org,
"Artem Mygaiev" <Artem_Mygaiev@epam.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Michal Orzel" <michal.orzel@amd.com>
Subject: Re: Coding Style Review and Automation
Date: Tue, 11 Feb 2025 11:03:47 +0000 [thread overview]
Message-ID: <Z6suNGMPoTVg2ND8@l14> (raw)
In-Reply-To: <Z6sY_YsjJ6rGi8zS@macbook.local>
On Tue, Feb 11, 2025 at 10:31:41AM +0100, Roger Pau Monné wrote:
> One question that seems to have been dropped from my previous email:
> would it be feasible to apply the updated style to newly added chunks
> of code only, but not to the (unmodified) surrounding context?
There's a tool that can format only one patch, `git-clang-format`.
https://clang.llvm.org/docs/ClangFormat.html#git-integration
This could help temporally, or as a way to format a patch under review
to get a better view of the new coding style (instead of having a whole
file been formatted which could make reviewing the new style harder).
Cheers,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2025-02-11 11:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 21:16 Coding Style Review and Automation Oleksandr Andrushchenko
2025-02-11 1:37 ` Stefano Stabellini
2025-02-11 9:01 ` Roger Pau Monné
2025-02-11 9:10 ` Luca Fancellu
2025-02-11 9:31 ` Roger Pau Monné
2025-02-11 9:49 ` Luca Fancellu
2025-02-11 10:26 ` Roger Pau Monné
2025-02-11 10:30 ` Jan Beulich
2025-02-11 11:03 ` Anthony PERARD [this message]
2025-02-11 10:19 ` Jan Beulich
2025-02-11 14:06 ` Roger Pau Monné
2025-02-11 18:54 ` Marek Marczykowski-Górecki
2025-02-12 11:54 ` Edwin Torok
2025-02-11 10:14 ` Jan Beulich
2025-02-11 10:35 ` Roger Pau Monné
2025-02-11 10:28 ` Jan Beulich
2025-02-11 22:33 ` Stefano Stabellini
2025-02-12 9:14 ` Roger Pau Monné
2025-02-12 11:14 ` Grygorii Strashko
2025-02-12 11:31 ` Roger Pau Monné
2025-02-13 6:43 ` Oleksandr Andrushchenko
2025-02-12 20:03 ` Oleksandr Andrushchenko
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=Z6suNGMPoTVg2ND8@l14 \
--to=anthony.perard@vates.tech \
--cc=Artem_Mygaiev@epam.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Luca.Fancellu@arm.com \
--cc=andr2000@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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.