From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: uncrustify all the things
Date: Fri, 12 Mar 2021 08:09:51 -0400 [thread overview]
Message-ID: <20210312120955.2712730-1-david@tethera.net> (raw)
This replaces and expands id:20210307171658.1084026-1-david@tethera.net
There has been some style drift in the intervening ~ 2 years since we
last did these. The addition of a line length limit also triggers some
changes.
compat and parse-date-time are unchanged since the last uncrustify run.
I did ignore a couple of suggestions from uncrustify. One is aligning
foo->bar->
flub->gub
as
foo->bar->
flub->gub
The other is line breaks in the table of status-codes in
lib/notmuch-private.h. I'm not sure the best approach to the latter.
I'll probabably apply these relatively quickly to minimimize the
amount of pain for people (like me) rebasing patch series against
master.
next reply other threads:[~2021-03-12 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 12:09 David Bremner [this message]
2021-03-12 12:09 ` [PATCH 1/4] lib: run uncrustify David Bremner
2021-03-12 12:09 ` [PATCH 2/4] util: " David Bremner
2021-03-12 12:09 ` [PATCH 3/4] test: " David Bremner
2021-03-12 12:09 ` [PATCH 4/4] cli: " David Bremner
2021-03-13 16:06 ` uncrustify all the things David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210312120955.2712730-1-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).