From: Leo Famulari <leo@famulari.name>
To: 51739@debbugs.gnu.org
Subject: [bug#51739] [PATCH 2/3] gnu: Use license: prefix.
Date: Wed, 10 Nov 2021 17:26:44 -0500 [thread overview]
Message-ID: <YYxHJFHl29Fthi1n@jasmine.lan> (raw)
In-Reply-To: <M5E9ow1MQ1Sa0sGmeKvrYIpbDY1IbRszq-AyliT0itqrCa_6p1Wo4T5_69970MvcguLImkm0A6nUisPwHHktEKgYgIgAQhef4fQLKWWzXvs=@protonmail.com>
On Wed, Nov 10, 2021 at 03:07:46AM +0000, phodina via Guix-patches via wrote:
> * gnu/packages/time.scm (time, python-pytimeparse, python-pytzdata,
> python2-tzdata, python-pytz, python2-pytz, python-pendulum, python-dateutil,
> python2-dateutil, python-parsedatetime, python2-parsedatetime,
> python-ciso8601, python-tzlocal, python-isodate, python2-isodate,
> python-iso8601, python2-iso8601, python-monotonic, python2-monotonic,
> python-pyrfc3339, python2-pyrfc3339, python-arrow, python-aniso8601,
> python2-aniso8601, datefudge, countdown) [license]: Prefix with license:.
Is there a reason to make this change? Usually we only prefix the
license field when necessary.
next prev parent reply other threads:[~2021-11-10 22:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 3:04 [bug#51739] [PATCH 1/3] gnu: Add realmd phodina via Guix-patches via
2021-11-10 3:07 ` [bug#51739] [PATCH 2/3] gnu: Use license: prefix phodina via Guix-patches via
2021-11-10 22:26 ` Leo Famulari [this message]
2021-11-10 3:08 ` [bug#51739] [PATCH 3/3] gnu: Add rdate phodina via Guix-patches via
2021-11-10 22:29 ` Leo Famulari
2021-11-10 22:33 ` [bug#51739] [PATCH 1/3] gnu: Add realmd Leo Famulari
2021-12-01 16:43 ` Ludovic Courtès
2021-12-01 16:42 ` Ludovic Courtès
2021-12-02 19:08 ` phodina via Guix-patches via
2021-12-02 19:13 ` phodina via Guix-patches via
2021-12-02 19:24 ` Leo Famulari
2021-12-02 21:50 ` phodina via Guix-patches via
2021-12-02 22:24 ` Leo Famulari
2021-12-03 14:17 ` phodina via Guix-patches via
2021-12-08 19:27 ` bug#51739: " Leo Famulari
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=YYxHJFHl29Fthi1n@jasmine.lan \
--to=leo@famulari.name \
--cc=51739@debbugs.gnu.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.
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.