From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] switch patch_args to -Np1
Date: Fri, 18 Jun 2021 05:57:33 +0200 [thread overview]
Message-ID: <20210618035733.S9pnawF0JZhlvRGBirptV0Fq0VB_urujKoqfyhDkov4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31550@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/31550#issuecomment-863736246
Comment:
> we should not do it this way, we should instead patch all the patches as needed
Yes, but I would like to do it step by step in order to limit the # of changes in each step. I.e. the next change will be patching the patch for packages start with "a".
next prev parent reply other threads:[~2021-06-18 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 1:38 [PR PATCH] " sgn
2021-06-18 2:41 ` q66
2021-06-18 3:57 ` sgn [this message]
2021-06-18 4:13 ` Vaelatern
2021-06-18 7:27 ` sgn
2021-06-18 11:30 ` [PR PATCH] [Updated] " sgn
2021-06-18 11:33 ` sgn
2021-06-18 11:39 ` q66
2021-06-18 12:03 ` [PR PATCH] [Updated] " sgn
2021-06-18 16:51 ` q66
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=20210618035733.S9pnawF0JZhlvRGBirptV0Fq0VB_urujKoqfyhDkov4@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).