From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: darcs
Date: Fri, 24 Feb 2017 18:59:49 +0000 [thread overview]
Message-ID: <20170224185949.piqnnpprfe345ifv@wasp> (raw)
I myself feel like I'm being repetive here,
but as it's still unsolved on how the curl issue in TOTAL will be
resolved, this should affect darcs merging into the tree.
It worked, except for the https hosts.
I can rebase my branch and push an renewed series to
'guix-patches@gnu.org' in hope that it doesn't fall to bitrot.
Or did you add any significant changes in the last months, Leo (or
whoever reviewed it back then)?
reply other threads:[~2017-02-24 18:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170224185949.piqnnpprfe345ifv@wasp \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.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).