From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 27227@debbugs.gnu.org
Subject: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.
Date: Sun, 4 Jun 2017 12:37:21 -0400 [thread overview]
Message-ID: <20170604163721.GC14880@jasmine> (raw)
In-Reply-To: <87k24ryigh.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
On Sun, Jun 04, 2017 at 03:45:50PM +0200, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > * gnu/packages/perl.scm (perl): Update to 5.26.0.
> > * gnu/packages/patches/perl-no-sys-dirs.patch: Update patch context for
> > 'hints/linux.sh'.
>
> LGTM.
Thanks!
Is core-updates still open for changes like this? Or should I wait until the
next cycle?
So far I built the final 'perl' package and am currently building Git with this
patch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-04 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 8:40 bug#27227: [PATCH] gnu: perl: Update to 5.26.0 Leo Famulari
2017-06-04 13:45 ` Marius Bakke
2017-06-04 16:37 ` Leo Famulari [this message]
2017-06-04 18:35 ` Marius Bakke
2017-06-04 19:19 ` Leo Famulari
2017-06-07 22:37 ` bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.] Leo Famulari
2017-06-08 0:25 ` bug#27282: Perl 5.26.0 "dotless @INC" Leo Famulari
2017-06-08 12:28 ` bug#27282: Perl 5.26.0 "dotless @INC" [was Re: bug#27227: [PATCH] gnu: perl: Update to 5.26.0.] Ludovic Courtès
2017-06-08 15:29 ` Leo Famulari
2017-06-12 2:48 ` Leo Famulari
2017-06-13 19:47 ` Leo Famulari
2017-06-14 7:38 ` Ludovic Courtès
2017-06-14 14:30 ` Leo Famulari
2017-08-02 22:10 ` Ludovic Courtès
2017-08-02 22:41 ` 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=20170604163721.GC14880@jasmine \
--to=leo@famulari.name \
--cc=27227@debbugs.gnu.org \
--cc=mbakke@fastmail.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.