From: Jeff King <peff@peff.net>
To: ZhenTian <loooseleaves@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: I lost my commit signature
Date: Wed, 15 Jun 2016 00:34:50 -0400 [thread overview]
Message-ID: <20160615043450.GA3975@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGrdoOoxphU0tRjV22yduXrhmOSyCc_zVnhuO9fFA6UPRd9WiA@mail.gmail.com>
On Wed, Jun 15, 2016 at 12:27:15PM +0800, ZhenTian wrote:
> I got two more lines from gpg -v during commit with -S:
> ```
> gpg: writing to stdout
> gpg: RSA/SHA1 signature from: "2EF2AD6E Tian Zhen <tianzhen@honovation.com>"
> ```
>
> after I commit, I push it to remote, but someone had pushed before to
> master branch, so I pull on master branch(`git pull --rebase`), then I
> check my commit via `git log --show-signature`, there is no signature
> in it, so I commit it with --ament and -S again, the signature is come
> back.
>
> I haven't check signature before push, because I have checked four
> commits before, every commit is fine.
>
> I don't know whether the `git pull` influenced signature or not.
Ah, so the problem is probably that you had a signature _initially_, but
that it did not survive the rebase. Which makes sense, as rebase would
need to re-sign. It does not by default, but you can tell it to do so
with "-S". Or you can set `commit.gpgsign`, which should sign in both
cases.
-Peff
next prev parent reply other threads:[~2016-06-15 4:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 7:50 I lost my commit signature ZhenTian
2016-06-14 7:58 ` Jeff King
2016-06-14 8:09 ` ZhenTian
2016-06-14 8:18 ` Jeff King
2016-06-14 8:39 ` ZhenTian
2016-06-14 9:41 ` Jeff King
2016-06-14 9:56 ` ZhenTian
2016-06-14 10:57 ` Michael J Gruber
2016-06-14 11:11 ` [PATCH] gpg-interface: check gpg signature for correct header Michael J Gruber
2016-06-14 11:20 ` Jeff King
2016-06-14 11:34 ` Michael J Gruber
2016-06-14 11:58 ` Michael J Gruber
2016-06-14 12:05 ` [PATCHv2] " Michael J Gruber
2016-06-14 14:44 ` [PATCHv3] gpg-interface: check gpg signature creation status Michael J Gruber
2016-06-14 18:13 ` Junio C Hamano
2016-06-14 21:50 ` Jeff King
2016-06-14 22:26 ` Jeff King
2016-06-14 23:47 ` Junio C Hamano
2016-06-15 0:56 ` Jeff King
2016-06-15 7:17 ` Michael J Gruber
2016-06-16 9:25 ` Jeff King
2016-06-16 11:30 ` Michael J Gruber
2016-06-15 3:28 ` Jeff King
2016-06-15 4:27 ` I lost my commit signature ZhenTian
2016-06-15 4:34 ` Jeff King [this message]
2016-06-15 7:07 ` Michael J Gruber
2016-06-15 10:36 ` ZhenTian
2016-06-16 7:34 ` Jeff King
2016-06-16 17:06 ` Junio C Hamano
2016-06-17 8:18 ` Michael J Gruber
2016-06-17 16:39 ` 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=20160615043450.GA3975@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=loooseleaves@gmail.com \
/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).