From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Eddie Monge <eddie@eddiemonge.com>, git@vger.kernel.org
Subject: Re: Git stash gpg prompting
Date: Fri, 30 May 2014 13:31:45 -0700 [thread overview]
Message-ID: <xmqqr43b80um.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140530202413.GD5513@sigill.intra.peff.net> (Jeff King's message of "Fri, 30 May 2014 16:24:14 -0400")
Jeff King <peff@peff.net> writes:
> However, I wonder if it is really ever going to be sane to set
> commit.gpgsign and not use something like gpg-agent.
>
> For example, if you
> were to ever "git rebase" a patch series (or even just use "git rebase
> -i" to refactor commits), you would be prompted for your passphrase to
> sign each individual patch.
Correct.
I actually doubt it is sane to set commit.gpgsign to true and trust
gpg-agent, but that is a separate issue.
prev parent reply other threads:[~2014-05-30 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 20:07 Git stash gpg prompting Eddie Monge
2014-05-30 20:24 ` Jeff King
2014-05-30 20:31 ` Junio C Hamano [this message]
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=xmqqr43b80um.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=eddie@eddiemonge.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).