all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Gabriel Wicki <gabriel@erlikon.ch>
Cc: vagrant@debian.org, 74329@debbugs.gnu.org
Subject: [bug#74329] [PATCH 1/2] gnu: Lint synopses.
Date: Tue, 10 Dec 2024 23:08:20 -0800	[thread overview]
Message-ID: <87h67au26z.fsf@wireframe> (raw)
In-Reply-To: <r5yqfuj77bsp6u5j2w5pvkucdu3uuhwh4sjjmca6yjxdrsr23s@53ci2hvht26e>

[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]

On 2024-11-12, Gabriel Wicki wrote:
> Subject: [PATCH 1/2] gnu: Lint synopses.
>
> Correct a bunch of synopses.
>
> Change-Id: I69fb52cc783994673e2eaf92b936edc19ba92cfe
> ---
>  gnu/packages/astronomy.scm          |  2 +-
...
>  gnu/packages/web.scm                |  2 +-
>  57 files changed, 175 insertions(+), 178 deletions(-)

Thanks! I think that alone cleared around 200 guix lint warnings!

Pushed as several split commits:

6f8c8a86d827627f503a803381bce7fbcf8f39a0 gnu: Fix synopsis in miscelaneous packages.
1b7c85f24ea6bf455a31cb289dabeadff27687f1 gnu: Fix synopsis in various go packages.
8d05f0c8db93ccd5350cb8968fd96957ea9820b2 gnu: Fix synopsis in various python packages.
2159d8fc03487da400e6694d522a41b934a2a1aa gnu: Fix synopsis in various julia packages.
3ba56d011e5b568f653c5d1cc54e407e2e9062da gnu: Fix synopsis in various texlive packages.
b158f3fb7acb8a9677898e3cfffd21abf55dbafa gnu: Fix synopsis in rust packages.
44cc1295752edb7711471dce4872c41d740d10d0 gnu: Fix synopsis in various sbcl packages.
5d77267abd2ec8a4537304c22118166cd74c1620 gnu: Fix synopsis in various emacs packages.
1199a19ba7a1486ef016e8991d21d53e9c7eb990 gnu: Fix synopsis in various haskell packages.

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 believe the changed files are more-or-less identical to what you
proposed, with only some minor rebasing needed.

In the future, somewhat smaller patch sets from the get-go would be
easier (and possibly quicker) to review and merge. Also, if the worst
happens, and it takes a long time to review (Like this time!
Oops. Sorry!), the individual patches might be more likely to merge
successfully than one or two huge mega-patches.

Still have to follow-up with the description patches (I did manage to
rebase it on a recent master, at least)... where I suspect I will have
more opinions... but that is for another day...

Thanks again!

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2024-12-11  7:50 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 [this message]
2024-12-11 11:37       ` Gabriel Wicki
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=87h67au26z.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=74329@debbugs.gnu.org \
    --cc=gabriel@erlikon.ch \
    /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.