From: Gabriel Wicki <gabriel@erlikon.ch>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 74329@debbugs.gnu.org
Subject: [bug#74329] [PATCH 1/2] gnu: Lint synopses.
Date: Wed, 11 Dec 2024 12:37:16 +0100 [thread overview]
Message-ID: <wwduxyj725js5ff3bn73twq6vx7ouwf6nqat5nza6tsdwp44sw@h2lagt5f2fge> (raw)
In-Reply-To: <87h67au26z.fsf@wireframe>
On Tue, Dec 10, 2024 at 11:08:20PM -0800, Vagrant Cascadian wrote:
> Thanks! I think that alone cleared around 200 guix lint warnings!
More than that - with my cleaning efforts, i also improved our linter,
since there were LOTS of false positives (or, the linter was just not
really up to the de facto standards in our codebase) - so i eliminated
the vast majority of lint warnings [0]
> I used guix.git/etc/committer.scm to help format the oh-so-verbose
> commit messages, and then squashed the resulting individual patches into
> several grouped semi-related patches, although it required a lot of
> massaging to get it "right". Clearly I had to make it hard on myself. :)
I didn't know about that script! And also I had no idea what the
simplest format for all those changes would have been - maybe i
should've asked in advance (: Grouping them by family definitely makes
sense.
Thanks for merging,
g
[0] https://issues.guix.gnu.org/74459
next prev parent reply other threads:[~2024-12-11 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 20:36 [bug#74329] [PATCH 0/2] Extensively lint descriptions and synopses Gabriel Wicki
[not found] ` <handler.74329.B.173144383113227.ack@debbugs.gnu.org>
2024-11-12 20:41 ` [bug#74329] [PATCH 1/2] gnu: Lint synopses Gabriel Wicki
2024-12-11 7:08 ` Vagrant Cascadian
2024-12-11 11:37 ` Gabriel Wicki [this message]
2024-11-12 20:42 ` [bug#74329] [PATCH 2/2] gnu: Lint descriptions Gabriel Wicki
2024-11-21 22:28 ` [bug#74329] resend? Gabriel Wicki
2024-11-21 22:30 ` [bug#74329] [PATCH 1/2] gnu: Lint synopses Gabriel Wicki
2024-11-21 22:31 ` [bug#74329] [PATCH 2/2] gnu: Lint descriptions Gabriel Wicki
2024-12-10 23:08 ` [bug#74329] [PATCH 0/2] Extensively lint descriptions and synopses Vagrant Cascadian
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=wwduxyj725js5ff3bn73twq6vx7ouwf6nqat5nza6tsdwp44sw@h2lagt5f2fge \
--to=gabriel@erlikon.ch \
--cc=74329@debbugs.gnu.org \
--cc=vagrant@debian.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.