From: Chris Marusich <cmmarusich@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 31284@debbugs.gnu.org
Subject: bug#31284: [PATCH 0/1] guix: Add git-fetch/impure.
Date: Sun, 29 Apr 2018 17:18:58 -0700 [thread overview]
Message-ID: <87h8nteebx.fsf@gmail.com> (raw)
In-Reply-To: <87efixykrk.fsf@netris.org> (Mark H. Weaver's message of "Sun, 29 Apr 2018 13:39:43 -0400")
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> Hi Chris,
>
> I don't see your patch anywhere in <https://bugs.gnu.org/31284>.
> Can you resend it?
>
> I'm curious how you arrange for a build process launched by guix-daemon
> to have access to your 'ssh-agent'. Although I've dropped my objection
> to this idea in principle, I have yet to review the technical details of
> how this actually works. It might be that the details will raise
> further alarm bells in my head :)
The patch can be found here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31285
I accidentally sent the cover letter to bug-guix@gnu.org instead of
guix-patches@gnu.org, which is why this bogus bug report (31284) was
opened. I've closed this bug report in favor of the "guix-patches" one.
Sorry for the confusion!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-04-30 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 8:12 bug#31284: [PATCH 0/1] guix: Add git-fetch/impure Chris Marusich
2018-04-27 8:19 ` bug#31284: Status: " Chris Marusich
2018-04-27 13:05 ` bug#31284: " Thompson, David
2018-04-28 4:45 ` Chris Marusich
2018-04-29 17:21 ` Ludovic Courtès
2018-04-27 21:37 ` Mark H Weaver
2018-04-29 17:39 ` Mark H Weaver
2018-04-30 0:18 ` Chris Marusich [this message]
[not found] <87o9i4szg8.fsf@gmail.com>
2018-04-29 17:28 ` Mark H Weaver
2018-04-30 13:59 ` Thompson, David
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=87h8nteebx.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=31284@debbugs.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).