From: Mark Wielaard <mark@klomp.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Simon Marchi <simark@simark.ca>,
Joel Brobecker <brobecker@adacore.com>,
Simon Marchi via Gdb <gdb@sourceware.org>
Subject: Re: Any concrete plans after the GDB BoF?
Date: Sun, 12 Feb 2023 13:43:45 +0100 [thread overview]
Message-ID: <20230212124345.GH2430@gnu.wildebeest.org> (raw)
In-Reply-To: <87mt5kunum.fsf@redhat.com>
Hi Andrew,
On Sat, Feb 11, 2023 at 05:13:37PM +0000, Andrew Burgess wrote:
> Simon Marchi via Gdb <gdb@sourceware.org> writes:
> > I would suggest mandating one version, and for that version to
> > continuously be the latest stable version of clang-format, like we do
> > for Black. When a new version comes out, we don't have to wonder if /
> > when we move the next version. Someone just pushes a patch re-formating
> > the code to the next version, if there are some differences. It keeps
> > the overhead to a minimum.
>
> I dislike our policy of using the latest version of black, and would
> argue that always using the latest version _increases_ the overhead,
> rather than reducing it.
Have you found the python formatting flagged by black "unstable"? The
buildbot uses the latest black as comes with fedora stable and I don't
remember it flagging issues on upgrades. But maybe it hasn't been
running for long enough? It has been running since July last year. Are
you running a much older black? Does it produce different formatting?
> If I had a choice then, personally, I'd vote against using clang-format
> at all, but it feels like there's a majority in favour, so if we do have
> to go down this route, I'd rather we adopted the same policy as for
> autotools and C++ versioning. That is, pick something that works for
> us, and commit to it over the medium term. That way at least, I can
> build a single version of clang-format and know that it's going to last
> me for a while.
But is there already a verions that works? I think that is the
difference between the python black formatter for python code and the
clang-format for C and C++ code. It seems for the python code there is
a supported format that matches what is used, but for clang-format
there is not (yet?).
Cheers,
Mark
next prev parent reply other threads:[~2023-02-12 12:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 10:47 Luis Machado
2022-10-28 16:16 ` Simon Marchi
2022-10-28 16:51 ` John Baldwin
2022-10-28 16:54 ` Simon Marchi
2022-10-31 9:28 ` Luis Machado
2022-10-31 13:17 ` Simon Marchi
2022-10-31 13:37 ` Joel Brobecker
2022-10-31 14:15 ` Simon Marchi
2022-10-31 17:31 ` Joel Brobecker
2023-02-11 17:13 ` Andrew Burgess
2023-02-12 12:43 ` Mark Wielaard [this message]
2023-02-13 11:54 ` Andrew Burgess
2023-02-13 12:52 ` Luis Machado
2023-02-13 14:24 ` Tom Tromey
2023-02-13 14:42 ` Luis Machado
2023-02-13 15:13 ` Andrew Burgess
2023-02-13 15:23 ` Luis Machado
2023-02-14 5:48 ` Joel Brobecker
2023-02-15 14:47 ` Andrew Burgess
2023-02-16 4:14 ` Joel Brobecker
2023-02-16 9:51 ` Mark Wielaard
2023-02-16 10:16 ` Joel Brobecker
2023-02-16 11:58 ` Eli Zaretskii
2023-02-16 13:31 ` Joel Brobecker
2023-02-16 15:23 ` Eli Zaretskii
2023-02-14 13:07 ` Mark Wielaard
2023-02-14 14:23 ` Pedro Alves
2023-02-14 13:00 ` Mark Wielaard
2023-02-15 14:36 ` Andrew Burgess
2023-02-13 14:05 ` Tom Tromey
2022-12-15 10:17 ` Luis Machado
2023-01-01 22:02 ` Mark Wielaard
2023-01-20 17:30 ` Tom Tromey
2023-01-20 20:30 ` Tom Tromey
2023-01-27 15:50 ` Lancelot SIX
2023-01-27 23:50 ` Tom Tromey
2023-01-30 17:43 ` Lancelot SIX
2023-01-30 18:46 ` Mark Wielaard
2023-01-30 21:08 ` Tom Tromey
2023-02-04 11:36 ` Mark Wielaard
2023-01-31 10:00 ` Lancelot SIX
2022-12-13 2:48 ` Frank Ch. Eigler
2023-02-16 8:53 anix
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=20230212124345.GH2430@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=aburgess@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=simark@simark.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).