git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: rebase has no --verify-signatures

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 8, 2015, 01:21 UTC
Message-ID
<20151208012125.GD990758@vauxhall.crustytoothpaste.net>
In-Reply-To
<20151207140015.GA14956@netblarch.tu-darmstadt.de>
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.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: Alexander 'z33ky' HirschNext: Alexander 'z33ky' Hirsch
Message 2 of 3 in “rebase has no --verify-signatures”
  1. Alexander 'z33ky' HirschDec 7, 2015
  2. brian m. carlsonDec 8, 2015
  3. Alexander 'z33ky' HirschDec 9, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.