From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 61684@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: bug#61684: can't compose 'with-patch' with 'with-source'
Date: Mon, 27 Feb 2023 15:12:29 +0100 [thread overview]
Message-ID: <87zg8zjiya.fsf@gnu.org> (raw)
In-Reply-To: <87cz5zgogo.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 24 Feb 2023 08:52:39 -0500")
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>> Quoting Ludo,
>>
>> (this is crucial for our HPC
>> users, who routinely combine a whole bunch of options; you have no idea
>> how far they go once you give them the tool :-))
>>
>> <https://issues.guix.gnu.org/msgid/871qmg79u7.fsf@gnu.org>
>>
>> and I agree with « you have no idea how far they go once you give them
>> the tool :-)) ».
>
> It seems a bit hypothetical at this point, so I wouldn't want to cripple
> the design by it.
It baffles me that you would consider other people’s experience as
“hypothetical”. It’s not, really.
The choice of words after the comma is also unfortunate in several ways.
Ludo’.
next prev parent reply other threads:[~2023-02-27 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 18:08 bug#61684: can't compose 'with-patch' with 'with-source' Maxim Cournoyer
2023-02-21 19:05 ` Simon Tournier
2023-02-23 14:08 ` Ludovic Courtès
2023-02-23 22:27 ` Maxim Cournoyer
2023-02-24 12:02 ` Simon Tournier
2023-02-24 13:21 ` Maxim Cournoyer
2023-02-24 13:43 ` Simon Tournier
2023-02-24 13:52 ` Maxim Cournoyer
2023-02-25 12:29 ` Simon Tournier
2023-02-25 19:43 ` Maxim Cournoyer
2023-02-27 14:12 ` Ludovic Courtès [this message]
2023-02-27 16:29 ` Maxim Cournoyer
2023-02-27 14:09 ` Ludovic Courtès
2023-02-28 10:00 ` Simon Tournier
2023-03-01 15:49 ` Ludovic Courtès
2023-02-24 13:59 ` Maxim Cournoyer
2023-03-03 9:43 ` Ludovic Courtès
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=87zg8zjiya.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=61684@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--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 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.