From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: ludo@gnu.org, Liliana Marie Prikler <liliana.prikler@gmail.com>,
58813@debbugs.gnu.org
Subject: bug#58813: [PATCH v2] doc: Document how to use Patman for patches submission.
Date: Wed, 08 Mar 2023 11:26:39 -0500 [thread overview]
Message-ID: <87jzzrus3k.fsf@gmail.com> (raw)
In-Reply-To: <865ybbaauy.fsf@gmail.com> (Simon Tournier's message of "Wed, 08 Mar 2023 09:47:01 +0100")
Hi Simon,
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi Liliana,
>
> On Wed, 08 Mar 2023 at 06:29, Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
>> Am Dienstag, dem 07.03.2023 um 18:39 +0100 schrieb Simon Tournier:
>
>>> I still think this documentation for configuring ’patman’ about
>>> “Patch management” is helpful. I think it could be part of the
>>> manual. If not for reasons I am missing, at least this documentation
>>> should be included in the Cookbook.
>>
>> There are two discussions here:
>>
>> 1. Should we "mandate" the use of patman?
I don't think this was ever in the discussion. The patch series I sent
only hinted at a tool that can provide some further automation. It's
not mandated (as in, required) at all. git send-email works just fine
when manually pasting the output of 'etc/teams.scm cc-members
the.patch', and will continue to even if we mention the tool 'patman' in
conjunction.
[...]
> Well, I do not have a strong opinion. On a side note, because I am
> lazy, if there is no pre-configuration that I can adapt, I will not try
> patman.
It's already there; see the .patman file at the root of the repo.
There's really not much to patman, it's a simple tool that does what it
does well (and already exists).
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-08 16:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 3:50 bug#58813: can't substitute etc/teams.scm command as doc suggests Maxim Cournoyer
2022-10-27 6:08 ` Liliana Marie Prikler
2022-10-27 12:40 ` Maxim Cournoyer
2022-10-27 16:27 ` Liliana Marie Prikler
2023-02-26 3:55 ` bug#58813: [PATCH] doc: Document how to use Patman for patches submission Maxim Cournoyer
2023-02-26 8:25 ` Liliana Marie Prikler
2023-02-26 17:11 ` Maxim Cournoyer
2023-02-27 0:45 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-02-27 16:43 ` Maxim Cournoyer
2023-03-03 9:54 ` Ludovic Courtès
2023-03-03 17:26 ` Liliana Marie Prikler
2023-03-06 14:53 ` bug#58813: ‘guix style’ flaws Ludovic Courtès
2023-03-06 17:42 ` Maxim Cournoyer
2023-03-07 1:07 ` bug#58813: [PATCH] doc: Document how to use Patman for patches submission Maxim Cournoyer
2023-03-10 9:01 ` Ludovic Courtès
2023-03-10 14:07 ` Maxim Cournoyer
2023-04-23 16:04 ` bug#58813: [PATCH 0/5] Fix teams.scm by use of a new --header-cmd git send-email option Maxim Cournoyer
2023-04-23 16:04 ` bug#58813: [PATCH 1/5] gnu: git: Apply patch adding the --header-cmd feature Maxim Cournoyer
2023-04-23 17:00 ` Liliana Marie Prikler
2023-04-24 0:46 ` Maxim Cournoyer
2023-04-23 16:04 ` bug#58813: [PATCH 2/5] teams: Add 'cc-members-header-cmd' action Maxim Cournoyer
2023-04-23 16:04 ` bug#58813: [PATCH 3/5] teams: Add a configure-git action Maxim Cournoyer
2023-04-23 17:03 ` Liliana Marie Prikler
2023-04-24 0:59 ` Maxim Cournoyer
2023-04-24 2:29 ` bug#58813: [PATCH v2 0/5] Fix teams.scm by use of a new --header-cmd git send-email option Maxim Cournoyer
2023-04-24 2:29 ` bug#58813: [PATCH v2 1/5] gnu: git: Apply patch adding the --header-cmd feature Maxim Cournoyer
2023-04-24 2:29 ` bug#58813: [PATCH v2 2/5] teams: Add 'cc-members-header-cmd' action Maxim Cournoyer
2023-04-24 2:29 ` bug#58813: [PATCH v2 3/5] Makefile.am: Auto-configure Git on 'make' Maxim Cournoyer
2023-04-24 4:22 ` Liliana Marie Prikler
2023-04-24 12:37 ` Maxim Cournoyer
2023-04-28 14:28 ` Josselin Poiret via Bug reports for GNU Guix
2023-05-01 16:38 ` bug#58813: can't substitute etc/teams.scm command as doc suggests Maxim Cournoyer
2023-04-24 2:29 ` bug#58813: [PATCH v2 4/5] teams: Add a 'cc-mentors-header-cmd' action Maxim Cournoyer
2023-04-24 2:29 ` bug#58813: [PATCH v2 5/5] doc: Simplify contributing section by automating git configuration Maxim Cournoyer
2023-04-23 16:04 ` bug#58813: [PATCH 4/5] teams: Add a 'cc-mentors-header-cmd' action Maxim Cournoyer
2023-04-23 16:04 ` bug#58813: [PATCH 5/5] doc: Simplify contributing section by automating git configuration Maxim Cournoyer
2023-03-07 11:35 ` bug#58813: [PATCH v2] doc: Document how to use Patman for patches submission Simon Tournier
2023-03-07 16:46 ` Maxim Cournoyer
2023-03-07 17:39 ` Simon Tournier
2023-03-08 5:29 ` Liliana Marie Prikler
2023-03-08 8:47 ` Simon Tournier
2023-03-08 16:26 ` Maxim Cournoyer [this message]
2023-03-08 17:05 ` Simon Tournier
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzzrus3k.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=58813@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).