Re: [PATCH v8 0/9] ssh signing: Add commit & tag signing/verification via SSH keys using ssh-keygen

[Junio C Hamano <gitster@pobox.com>]

Fabian Stelzer <fs@gigacodes.de> writes:

> Sorry, i think i'm just not familiar with the process. What do i do when
> the patch is in next and someone (or myself) find other bugs during testing?
> Do i send a new patch based on "next" or update my patchset but not
> squashing the fixup commits?

In general, you'd send an incremental update on top of what you
submitted and has been queued in my tree so far.  Looking for the
merge of the topic from the tip of 'next':

  $ git show -s "next^{/^Merge branch 'fs/ssh-signing' into next}" |
    grep "^Merge:"
  Merge: 348fe07b87 b88bcd013b
  $ git log --oneline --reverse master..b88bcd013b
  c222385164 ssh signing: preliminary refactoring and clean-up
  3a3fdc0b4e ssh signing: add test prereqs
  c7e2d30efe ssh signing: add ssh key format and signing code
  5493722122 ssh signing: retrieve a default key from ssh-agent
  6869f1f60c ssh signing: provide a textual signing_key_id
  9048bb3c9b ssh signing: verify signatures using ssh-keygen
  587967698a ssh signing: duplicate t7510 tests for commits
  52ac6bd36f ssh signing: tests for logs, tags & push certs
  b88bcd013b ssh signing: test that gpg fails for unknown keys

we learn that b88bcd013b is the tip, so you'd send follow-up patches
to either fix a bug that exists in the tree of b88bcd013b, or enhance
a feature on top of the tree of b88bcd013b.

But since I am already ejecting the previous round out of 'next',
let's remember to do so the next time.  We will have to wait until
mid October (if I recall what I thought I read from you correctly)
anyway, so until then we can iterate outside the 'next' branch.

Thanks.