From: Marius Bakke <mbakke@fastmail.com>
To: julien lepiller <julien@lepiller.eu>, 26896@debbugs.gnu.org
Subject: bug#26896: php: Update to 7.1.5
Date: Fri, 12 May 2017 13:42:49 +0200 [thread overview]
Message-ID: <87y3u2i9mu.fsf@fastmail.com> (raw)
In-Reply-To: <02eed4e71590590297934ededfb8d950@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
julien lepiller <julien@lepiller.eu> writes:
> Hi,
>
> php 7.1.5 has just been annonced. Here is a patch to update.
Thanks! Make sure to mention the change to [arguments] in the commit
message.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2017-05-12 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 11:24 bug#26896: php: Update to 7.1.5 julien lepiller
2017-05-12 11:42 ` Marius Bakke [this message]
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=87y3u2i9mu.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=26896@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).