From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCHv2] push: heed user.signingkey for signed pushes
Date: Fri, 24 Oct 2014 09:48:50 -0700 [thread overview]
Message-ID: <xmqqk33ph0r1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <544A6D4E.7070408@drmicha.warpmail.net> (Michael J. Gruber's message of "Fri, 24 Oct 2014 17:16:30 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> If I do that, I get:
>
> gpg: can't create `/home/mjg/src/git/t/trash
> directory.t5534-push-signed/gpghome/random_seed': Permission denied
>
> So I we do copy the env around. Problems arise only when the original
> copy ends up ro. We can guard against that by doing:
Ah, thanks for digging it further.
next prev parent reply other threads:[~2014-10-24 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:47 [RFD/PATCH] push: heed user.signingkey for signed pushes Michael J Gruber
2014-10-22 14:57 ` [PATCHv2] " Michael J Gruber
2014-10-22 22:05 ` Junio C Hamano
2014-10-22 23:47 ` Junio C Hamano
2014-10-24 15:16 ` Michael J Gruber
2014-10-24 15:23 ` [PATCH] t/lib-gpg: make gpghome files writable Michael J Gruber
2014-10-24 16:48 ` Junio C Hamano [this message]
2014-10-24 15:03 ` [PATCHv2] push: heed user.signingkey for signed pushes Michael J Gruber
2014-10-24 16:49 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk33ph0r1.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).