From: Alexander 'z33ky' Hirsch <1zeeky@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: rebase has no --verify-signatures
Date: Thu, 10 Dec 2015 00:20:15 +0100 [thread overview]
Message-ID: <20151209232015.GA1923@blarch> (raw)
In-Reply-To: <20151208012125.GD990758@vauxhall.crustytoothpaste.net>
On Tue, Dec 08, 2015 at 01:21:25AM +0000, brian m. carlson wrote:
> On Mon, Dec 07, 2015 at 03:00:15PM +0100, Alexander 'z33ky' Hirsch wrote:
> > Is there any technical reason why rebase should not have a
> > --verify-signatures flag? I have written a patch to git-rebase--am
> > which enables it to do such a check. If there is no reason not to
> > include it I'd add documentation and a test and submit it.
>
> As far as I know, there is no technical reason that it shouldn't. It's
> probably that nobody has implemented it yet. I'd certainly be
> interested in such a patch.
>
> For a thorough change, you'd probably want to make it work with
> git-rebase--merge and git-rebase--interactive as well. I'm sure I'm not
> the only person who frequently uses rebase -m.
Ah, rebase -m. That sounds nice, I didn't know about this feature.
In fact, I first tried to write the code in git-rebase--merge, thinking this is the default rebase script.
git-rebase--interactive sounds a bit more difficult since you could easily modify commits, thereby removing previously GPG signed commits. Although this sounds like all the more reason why it would be useful to check for it.
I'll look at the script and ponder about it. I'll post whatever I come up with on Thursday (probably) or Friday.
I'll put you in the CC when I post the patch.
Regards,
Alexander Hirsch
prev parent reply other threads:[~2015-12-09 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 14:00 rebase has no --verify-signatures Alexander 'z33ky' Hirsch
2015-12-08 1:21 ` brian m. carlson
2015-12-09 23:20 ` Alexander 'z33ky' Hirsch [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=20151209232015.GA1923@blarch \
--to=1zeeky@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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).