From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: Automatic code formatting
Date: Sun, 10 Jul 2022 15:08:05 -0700 [thread overview]
Message-ID: <xmqqo7xwpqnu.fsf@gitster.g> (raw)
In-Reply-To: <YstJl+5BPyR5RWnR@tapette.crustytoothpaste.net> (brian m. carlson's message of "Sun, 10 Jul 2022 21:50:15 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I should point out that most platforms (and all major platforms) have
> clang and therefore I think clang-format should be a fine choice. It's
> highly configurable and will let us pick a style that most resembles the
> one we have now. However, I'm not picky and if we like something else
> better, great. As long as the option we pick is shipped in Debian, I'm
> for it.
As long as the options in clang-format we choose to use would
reformat the current codebase without disrupting too much, I would
be happy to see this done. It would probably need a bit of work but
hopefully clang-format is flexible enough to accomodate our style to
allow us do this.
next prev parent reply other threads:[~2022-07-10 22:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 21:50 Automatic code formatting brian m. carlson
2022-07-10 22:08 ` Junio C Hamano [this message]
2022-07-10 22:13 ` rsbecker
2022-07-11 0:58 ` brian m. carlson
2022-07-11 1:28 ` rsbecker
2022-07-11 16:53 ` Elijah Newren
2022-07-11 20:15 ` Ævar Arnfjörð Bjarmason
2022-07-11 21:19 ` Elijah Newren
2022-07-11 11:37 ` [RFC PATCH 0/4] make headway towards a clean "clang-format" Ævar Arnfjörð Bjarmason
2022-07-11 11:37 ` [RFC PATCH 1/4] Makefile: add a style-all targets for .clang-format testing Ævar Arnfjörð Bjarmason
2022-07-11 11:37 ` [RFC PATCH 2/4] .clang-format: Add a BitFieldColonSpacing=None rule Ævar Arnfjörð Bjarmason
2022-07-11 22:42 ` brian m. carlson
2022-07-11 22:52 ` Junio C Hamano
2022-07-12 6:56 ` Ævar Arnfjörð Bjarmason
2022-07-11 11:37 ` [RFC PATCH 3/4] .clang-format: do not enforce a ColumnLimit Ævar Arnfjörð Bjarmason
2022-07-11 21:37 ` Junio C Hamano
2022-07-12 7:03 ` Ævar Arnfjörð Bjarmason
2022-07-11 22:39 ` brian m. carlson
2022-07-11 22:46 ` Junio C Hamano
2022-07-11 23:05 ` Eric Sunshine
2022-07-11 23:30 ` Junio C Hamano
2022-07-11 11:37 ` [RFC PATCH 4/4] .clang-format: don't indent "goto" labels Ævar Arnfjörð Bjarmason
2022-07-11 21:04 ` Junio C Hamano
2022-07-12 6:55 ` Ævar Arnfjörð Bjarmason
2022-07-11 13:17 ` Automatic code formatting Phillip Wood
2022-07-11 13:21 ` Ævar Arnfjörð Bjarmason
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=xmqqo7xwpqnu.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).