From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Guix-devel <guix-devel@gnu.org>
Cc: blake@reproduciblemedia.com,
"Julien Lepiller" <julien@lepiller.eu>,
"Ludovic Courtès" <ludo@gnu.org>,
"Philip McGrath" <philip@philipmcgrath.com>
Subject: Re: [PATCH] doc: Update contribution guidelines on patches, etc.
Date: Tue, 9 Aug 2022 22:30:15 +0200 [thread overview]
Message-ID: <77ee6166-a430-a00f-0bac-243fd940df83@telenet.be> (raw)
In-Reply-To: <f4fd706dd08e2bc194b1f697bf2cfed220e037ae.camel@gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1442 bytes --]
On 09-08-2022 21:08, Liliana Marie Prikler wrote:
>>>> On 06-08-2022 08:55, Liliana Marie Prikler wrote:
>>>>
>>>>
>>>>> +If your package has a bug that takes multiple lines to fix,
>>>> I don't think this is true for replacing all instances of "foo"
>>>> by
>>>> "/gnu/store/.../bin/foo" in a file.
>>> Should it?
>> I don't think so. Directly substituting all the instances instead of
>> first writing a patch that does "foo" -> "@foo@" or such seems
>> simpler to me. This might be a bit too nit-picky though, maybe it's
>> clear from context that this is not the kind of fix meant by that
>> line.
> I'm struggling to see the issue here. For starters, it doesn't take
> multiple lines to embed a store path, the change usually happens on a
> single line. Of course, translating this into a substitute*, you
> expand this single line into multiple ones, but that's not what is
> meant here.
I was thinking of files that contain multiple instances of "foo"
(usually on multiple lines) to be replaced by "/gnu/store/.../bin/foo",
not files were a "foo
bar" was broken over multiple lines and it needs to be replaced by
"/gnu/store/.../bin/foo
bar".
At least for the former, I don't think an intermediate "@foo@" is useful
(with some exceptions, when a pattern match would catch too much).
The latter could in principle happen, but it doesn't seem to happen in
practice.
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 2577 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-09 21:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 3:17 A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches Maxime Devos
2022-07-25 5:21 ` Julien Lepiller
2022-07-25 11:18 ` Maxime Devos
2022-07-25 11:37 ` Julien Lepiller
2022-08-04 8:51 ` Ludovic Courtès
2022-08-05 3:23 ` Philip McGrath
2022-08-05 8:13 ` Maxime Devos
2022-08-05 3:38 ` Philip McGrath
2022-08-05 8:09 ` Maxime Devos
2022-08-05 10:18 ` Maxime Devos
2022-08-05 13:59 ` v2: " Maxime Devos
2022-08-06 6:55 ` [PATCH] doc: Update contribution guidelines on patches, etc Liliana Marie Prikler
2022-08-06 6:55 ` [PATCH v2] " Liliana Marie Prikler
2022-09-02 13:12 ` Ludovic Courtès
2022-09-02 18:05 ` Maxime Devos
2022-09-05 9:47 ` Ludovic Courtès
2022-09-05 13:12 ` Maxime Devos
2022-09-05 16:05 ` Maxime Devos
2022-08-09 16:45 ` [PATCH] " Maxime Devos
2022-08-09 17:05 ` Liliana Marie Prikler
2022-08-09 18:19 ` Maxime Devos
2022-08-09 19:08 ` Liliana Marie Prikler
2022-08-09 20:30 ` Maxime Devos [this message]
2022-08-10 4:25 ` Liliana Marie Prikler
2022-08-09 20:40 ` Maxime Devos
2022-08-08 21:51 ` v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches Andreas Enge
2022-08-09 15:06 ` Maxime Devos
2022-08-09 17:10 ` Andreas Enge
2022-09-05 13:03 ` Maxime Devos
2022-09-07 12:17 ` Andreas Enge
2022-09-07 18:08 ` Maxime Devos
2022-08-09 18:58 ` david larsson
2022-08-09 20:53 ` Maxime Devos
2022-08-10 11:23 ` david larsson
2022-08-05 16:59 ` blake
2022-08-09 16:30 ` Maxime Devos
2022-09-05 14:06 ` Maxime Devos
2022-08-10 6:10 ` blake
2022-08-10 9:06 ` Maxime Devos
2022-08-10 10:33 ` blake
2022-08-10 10:44 ` Maxime Devos
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=77ee6166-a430-a00f-0bac-243fd940df83@telenet.be \
--to=maximedevos@telenet.be \
--cc=blake@reproduciblemedia.com \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.org \
--cc=philip@philipmcgrath.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).