From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 66359@debbugs.gnu.org
Subject: [bug#66359] [PATCH] gnu: curl: Update to 8.3.0.
Date: Fri, 06 Oct 2023 11:55:14 +0200 [thread overview]
Message-ID: <20d7107dea14e1d879a08f562848cc0b5bf57a1d.camel@gmail.com> (raw)
In-Reply-To: <CAJ3okZ39D+99jx9JqodcPG9xVJR2y06+eWBqaWm9VAQadtVtgg@mail.gmail.com>
Am Freitag, dem 06.10.2023 um 11:09 +0200 schrieb Simon Tournier:
> Hi Liliana,
>
> On Fri, 6 Oct 2023 at 10:54, Liliana Marie Prikler
> <liliana.prikler@gmail.com> wrote:
>
> > > Naive question, why %version and not version?
> >
> > Because version gets shadowed by (package …). I could reorder the
> > fields in a non-standard way, but that'd be even less readable,
> > therefore the extra variable.
>
> Ah, I see. Thanks for explaining.
>
> Well, %something is usually for "global" parameters. At least, that
> the convention with Guix. Therefore, I would suggest to not use it
> in order to avoid confusion.
As far as I understand %something means "implementation detail" and
*something* means global, important something, but I might be mistaken
about that.
> Why not "this-version"?
Ain't nobody got time to type that.
next prev parent reply other threads:[~2023-10-06 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 6:11 [bug#66359] [PATCH] gnu: curl: Update to 8.3.0 Liliana Marie Prikler
2023-10-05 7:19 ` Efraim Flashner
2023-10-05 7:44 ` bug#66359: " Liliana Marie Prikler
2023-10-05 16:26 ` [bug#66359] " Simon Tournier
2023-10-06 8:54 ` Liliana Marie Prikler
2023-10-06 9:09 ` Simon Tournier
2023-10-06 9:55 ` Liliana Marie Prikler [this message]
2023-10-06 10:15 ` Simon Tournier
2023-10-09 12:33 ` [bug#66359] meaning of %something? (was Re: [bug#66359] [PATCH] gnu: curl: Update to 8.3.0.) Simon Tournier
2023-10-09 16:57 ` Liliana Marie Prikler
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=20d7107dea14e1d879a08f562848cc0b5bf57a1d.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=66359@debbugs.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).