Skip to content

Tags: LukeShu/git

Tags

lukeshu/next/2021-05-15

Toggle lukeshu/next/2021-05-15's commit message
subtree: handle pointing it at a file

lukeshu/next/2021-05-13

Toggle lukeshu/next/2021-05-13's commit message
subtree: better replace fix

lukeshu/next/2021-05-12

Toggle lukeshu/next/2021-05-12's commit message
subtree: fix for older Bash

lukeshu/next/2021-05-11

Toggle lukeshu/next/2021-05-11's commit message
less strict

lukeshu/next/2021-04-29

Toggle lukeshu/next/2021-04-29's commit message
Merge branches 'lukeshu/to-upstream/signed-commits', 'lukeshu/to-upst…

…ream/tag-names-v2' and 'lukeshu/subtree-2021-04/everything' into lukeshu/next

lukeshu/to-upstream/signed-commits/v1

Toggle lukeshu/to-upstream/signed-commits/v1's commit message
fast-export, fast-import: implement signed-commits

fast-export has an existing --signed-tags= flag that controls how to
handle tag signatures.  However, there is no equivalent for commit
signatures; it just silently strips the signature out of the commit
(analogously to --signed-tags=strip).

While signatures are generally problematic for fast-export/fast-import
(because hashes are likely to change), if they're going to support tag
signatures, there's no reason to not also support commit signatures.

So, implement signed-commits.

On the fast-export side, try to be as much like signed-tags as possible,
in both implementation and in user-interface; with the exception that
the default should be `--signed-commits=strip` (compared to the default
`--signed-tags=abort`), in order to continue defaulting to the
historical behavior.  Only bother implementing "gpgsig", not
"gpgsig-sha256"; the existing signed-tag support doesn't implement
"gpgsig-sha256" either.

On the fast-import side, I'm not entirely sure that I got the ordering
correct between "gpgsig" and "encoding" when generating the commit
object.

Signed-off-by: Luke Shumaker <lukeshu@datawire.io>

lukeshu/subtree-2020-08-20

Toggle lukeshu/subtree-2020-08-20's commit message
subtree: Add a --notree flag