From: Ricardo Wurmus <rekado@elephly.net>
To: 55379@debbugs.gnu.org
Subject: [bug#55379] [PATCH 01/14] gnu: Add r-gpg.
Date: Sun, 18 Dec 2022 09:58:47 +0100 [thread overview]
Message-ID: <87tu1tniog.fsf@elephly.net> (raw)
In-Reply-To: <d28d8263c5619db922a5ca3aa494fb96dd13786d.1651893550.git.kyle@posteo.net>
Hi Kyle,
I’ve been trying to apply these patches but haven’t been successful.
Have they been generated with “git format-patch”? It looks like they
haven’t. You can generate a patch series for the last 14 commits with
“git format-patch -14”, for example. To send an updated patch set you
can use “--reroll-count” (or “-v”), e.g. “--reroll-count 2”. This
generates emails with “[PATCH v2 …]” subjects, so we can automatically
extract all patches belonging to this new patch set.
I would be very happy if you could refresh this patch set on top of the
current “master” branch.
Please add each package definition to the file in alphabetic order. It
simplifies future maintenance.
I see that the descriptions contain straight single quotes for procedure
names and package names. We prefer to use texinfo syntax for procedures
instead, e.g. “@code{glm()}” instead of “'glm()'”. There are also some
packages that have only sentence fragments for descriptions (e.g. r-ca).
Could you please turn those into complete sentences? A common fix is to
prefix the description with “This package provides”.
Thanks!
--
Ricardo
prev parent reply other threads:[~2022-12-18 9:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 2:10 [bug#55379] [PATCH 01/14] gnu: Add r-gpg kyle
2022-05-12 2:10 ` [bug#55380] [PATCH 02/14] gnu: Add r-piton kyle
2022-12-29 19:47 ` bug#55380: " Ricardo Wurmus
2022-05-12 2:10 ` [bug#55379] [PATCH 03/14] gnu: Add r-tidyxl kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 04/14] gnu: Add r-unpivotr kyle
2022-05-14 10:53 ` Maxime Devos
2022-05-18 1:09 ` Kyle Andrews
2022-05-12 2:10 ` [bug#55381] [PATCH 05/14] gnu: Add r-unglue kyle
2022-05-14 18:18 ` Maxime Devos
2022-05-15 16:38 ` Kyle Andrews
2022-12-29 19:56 ` bug#55381: " Ricardo Wurmus
2022-05-12 2:10 ` [bug#55379] [PATCH 06/14] gnu: Add r-vcdextra kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 07/14] gnu: Add r-ca kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 08/14] gnu: Add r-qvcalc kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 09/14] gnu: Add r-gnm kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 10/14] gnu: Add r-relimp kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 11/14] gnu: Add r-picosat kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 12/14] gnu: Add r-ryacas kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 13/14] gnu: Add r-showimage kyle
2022-05-12 2:10 ` [bug#55379] [PATCH 14/14] gnu: Add r-genoud kyle
2022-05-13 7:10 ` [bug#55379] [PATCH 01/14] gnu: Add r-gpg Maxime Devos
[not found] ` <87bkw0jb3i.fsf@posteo.net>
2022-05-14 18:02 ` Maxime Devos
2022-05-15 16:24 ` Kyle Andrews
2022-05-14 18:07 ` Maxime Devos
2022-12-18 8:58 ` Ricardo Wurmus [this message]
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=87tu1tniog.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=55379@debbugs.gnu.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.