From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Update Git to 2.9.0
Date: Sun, 19 Jun 2016 13:41:28 -0400 [thread overview]
Message-ID: <20160619174128.GA28440@jasmine> (raw)
In-Reply-To: <87mvmhz39m.fsf@gnu.org>
On Sun, Jun 19, 2016 at 04:01:25PM +0200, Ludovic Courtès wrote:
> Sounds reasonable; ‘git commit’ still honors ‘commit.gpgsign’, right?
Yes, that still works as expected, at least in the simple case.
> > The commit text seems to imply that `git rebase` would no longer re-sign
> > commits, but that's not the case from my tests.
>
> OK. It would be bad if ‘git rebase’ would silently discard signatures.
> Thanks for paying attention to this!
I'm not sure what you mean exactly. If you rebase some signed commits,
the commits whose history changes will lose their signatures, because
they are no longer the same commits. But, I noticed this with previous
versions of Git also.
Because we never rewrite history once it's been on Savannah's master
branch, the only commits that need to be re-signed after rebase are my
own commits, so far seen only on my local repo. I've never needed to
rebase others' commits, so their signatures are unaffected.
Does that make sense?
next prev parent reply other threads:[~2016-06-19 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 22:13 [PATCH 0/1] Update Git to 2.9.0 Leo Famulari
2016-06-17 22:13 ` [PATCH 1/1] gnu: git: Update " Leo Famulari
2016-06-19 14:01 ` [PATCH 0/1] Update Git " Ludovic Courtès
2016-06-19 17:41 ` Leo Famulari [this message]
2016-06-20 8:13 ` Ludovic Courtès
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=20160619174128.GA28440@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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).