From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Artem Mygaiev <Artem_Mygaiev@epam.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Andrushchenko <andr2000@gmail.com>
Subject: Re: Coding Style Review and Automation
Date: Tue, 11 Feb 2025 11:35:44 +0100 [thread overview]
Message-ID: <Z6soAEIPFbB23S3S@macbook.local> (raw)
In-Reply-To: <e70af3df-d581-4f6e-bfc1-55484eff5d40@suse.com>
On Tue, Feb 11, 2025 at 11:14:55AM +0100, Jan Beulich wrote:
> On 11.02.2025 10:01, Roger Pau Monné wrote:
> > Is it possible for clang-format to be applied exclusively to newly
> > added chunks of code, while keeping the surroundings untouched?
>
> I, too, was wondering about this, at least as a data point. However,
> especially for files that aren't in a single style (e.g. where we're
> slowly transitioning from Linux to Xen style) this would then mean
> (at least) three styles in a single file.
My expectation is that the proposed clang-format based style will be
very close to the current Xen style. Maybe that's unrealistic, that's
why I requested a list of differences between our current coding style
and what clang-format can do.
Thanks, Roger.
next prev parent reply other threads:[~2025-02-11 10:36 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
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é [this message]
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=Z6soAEIPFbB23S3S@macbook.local \
--to=roger.pau@citrix.com \
--cc=Artem_Mygaiev@epam.com \
--cc=andr2000@gmail.com \
--cc=jbeulich@suse.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.