From: Ian Denhardt <ian@zenhack.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ntp
Date: Sat, 18 Oct 2014 14:08:13 -0400 [thread overview]
Message-ID: <20141018180813.28846.32077@vulcan.local.tld> (raw)
In-Reply-To: <87egu5qraf.fsf@yeeloong.lan>
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
Quoting Mark H Weaver (2014-10-18 12:24:56)
> (string-join (take (string-split version #\.) 2)
> ".")
<snip>
> I suppose we should add a procedure specifically for this, but
> it can wait, and it should be in a separate commit anyway.
I'm going to grab this and try to have a patch submitted today or
tomorrow. Does guix/utils.scm seem like a sensible place to put this?
-Ian
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAABAgAGBQJUQqyNAAoJEPZUuMfUyjy43CYP/R1LPUDdtDIgojVEEooQ5AiM
rPb9wBO4Q/Rn6ct7eEydt777guixAEjPDIIBK/6NUncOQ56bY9sbrYeAkObV/+2v
NP/2RKyBs1C2clNBYUeV+WVx0i1kAtfWZOUe4l7OnKOKaLcZ2yh6GfZXkTd6Oz33
GFI2mj7RYvgHYjrRytXVMya0IM3q/hz3cGLTTVxipFtqno0blG9x+SySZVSVHW26
KXiiVkAxbreIeGmCPprKr2F16IeKfiZPP538wtR4CyVJkL+mtosL1UboEZi2Ehe5
l8oalk8H0HHKqQvMVzJBn1y32nxSBsowuZ1N+Ye6JjLFA6Ket68BZP1X4KKusx3r
iPzJnYz2g9g8Tr+1Qy9DseOZGEcmhhYrpZFFKlYtDvoXataPpBUJ671KWJUmnuAR
CjTosO/F7C1DuFrBpZz0jZ0tDY1JiqpRNZw+TRjiBWm2R/CTN39++KwEeavTNQ2l
jIUhSM133Ay15zdzgS4CGnPXbbbkL9ol5R2y+rtlM/VcTFlCuxu2nlrYl5JWuXzg
7JdQ/CooPkrgs7yZ71KBaPWEdTMv8k712WbjwA/8qOuwScAJYvBUUhShyCyVUE6b
KLHcoXqkeEBxhTZE6kununmKe/p67bvsfKt2XjagHP1xiq0JbyOWOzUy6ty1TNBC
rGotZ4lAGBUodv43MGfo
=DMux
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-10-18 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 15:11 [PATCH] gnu: Add ntp John Darrington
2014-10-18 16:24 ` Mark H Weaver
2014-10-18 18:08 ` Ian Denhardt [this message]
2014-10-18 22:03 ` Mark H Weaver
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=20141018180813.28846.32077@vulcan.local.tld \
--to=ian@zenhack.net \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 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).