From: Mathieu Lirzin <mthl@openmailbox.org>
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: xz: Update to 5.2.1
Date: Sat, 12 Sep 2015 10:13:49 +0200 [thread overview]
Message-ID: <87egi4hx6q.fsf@openmailbox.org> (raw)
In-Reply-To: <87r3m4noab.fsf@gmail.com> ("宋文武"'s message of "Sat, 12 Sep 2015 14:29:32 +0800")
宋文武 <iyzsong@gmail.com> writes:
> This seem trigger the rebuild of everything, should I push it into
> the current 'core-updates' or wait for a next cycle?
This doesn't respond to your question, but could I suggest the
reformatting of the 'origin' S-expression? Like recently described
here... :)
<https://lists.gnu.org/archive/html/guix-devel/2015-09/msg00284.html>
Thanks,
--
Mathieu Lirzin
next prev parent reply other threads:[~2015-09-12 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 6:29 [PATCH] gnu: xz: Update to 5.2.1 宋文武
2015-09-12 8:13 ` Mathieu Lirzin [this message]
2015-09-12 11:56 ` 宋文武
2015-09-12 12:58 ` Mathieu Lirzin
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=87egi4hx6q.fsf@openmailbox.org \
--to=mthl@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@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).