From: Andreas Enge <andreas@enge.fr>
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: cmake: Update to 3.1.3.
Date: Thu, 26 Feb 2015 16:03:15 +0100 [thread overview]
Message-ID: <20150226150315.GA15436@debian> (raw)
In-Reply-To: <1424960281-10505-1-git-send-email-iyzsong@gmail.com>
On Thu, Feb 26, 2015 at 10:18:01PM +0800, 宋文武 wrote:
> * gnu/packages/cmake.scm (cmake): Update to 3.1.3.
Excellent, it all looks good! Do you think it would be useful to create a
wip-cmake branch first and to build it on hydra, to see whether there will be
many breakages in our existing packages, or do you think the risk is
sufficiently low to push to master directly?
Thanks!
Andreas
next prev parent reply other threads:[~2015-02-26 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 14:18 [PATCH] gnu: cmake: Update to 3.1.3 宋文武
2015-02-26 15:03 ` Andreas Enge [this message]
2015-02-26 15:41 ` Mark H Weaver
2015-02-26 15:55 ` Andreas Enge
2015-02-26 22:09 ` Andreas Enge
2015-02-27 11:29 ` 宋文武
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=20150226150315.GA15436@debian \
--to=andreas@enge.fr \
--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).