Hi Martin,
> I looked into this test in a bit more detail, and it seems to be quite
> hard to get right. Part of the reason is that `git commit-tree` requires
> a bit more careful use than `git commit`, but part of it is that the
> tests that we already have for `git commit-tree [-S]` right before the
> ones you're adding are a bit too loose, IMHO. So they're not ideal for
> copy-pasting... I've come up with the patch below, which you might want
> to use as a basis for your work.
>
> That is, you could `git am --scissors` this patch on a fresh branch and
> `git commit --amend --signoff --no-edit` it (see
> Documentation/SubmittingPatches, "forwarding somebody else's patch"),
> then base your work on it, e.g., by cherry-picking your v3 commit.
>
> I think you would want to add 2x3 lines of tests (3 for `--gpg-sign`, 3
> for `--gpg-sign=...`). That would give you eleventh-signed and
> twelfth-signed and you wouldn't need any invocation of `git commit` (so
> no thirteenth-signed).
Just finished adding in the changes you suggested, and everything looks
good on my end. I based my changes on the patch you provided.
> Or, a bit simpler:
>
> oid=$(echo 10 | git commit-tree -S HEAD^{tree}) &&
> git tag tenth-signed "$oid"
Just noticed your latest email. Do you prefer it this way? If so, I can amend
what I have before I submit v4.
When I submit v4, should I submit the patch you created as well, given
that my changes are based off of it?
Brandon
