[Patch git-remote-gcrypt] support commit history in commit message

[Tobias Birchler]

Hi Sean,

> I already discussed a very similar patch with one of your colleagues, I
believe.

Oh nice so he did submit. We weren't sure.
We improve upon the previous version with several bugfixes, the test suite
and the documentation. We also tested everything against a GitLab server.

> We concluded that the pre-receive hook and the commit history
> in the commit message did not achieve its intended purposes, once you
> think carefully about exactly what is trusting what.

Would you be so kind and provide a log or summary of your discussion so
that we can properly respond? Unfortunately we do not have a way to contact
the mentioned colleague.

Best,
Tobias

On Fri, 16 Sept 2022, 02:01 Sean Whitton, <spwhitton at spwhitton.name> wrote:

> Hello Tobias,
>
> On Thu 15 Sep 2022 at 04:40PM +02, Tobias Birchler wrote:
>
> > We implemented an additional feature for git-remote-gcrypt. The attached
> patch
> > adds the (optional) functionality of maintaining a commit history in the
> commit
> > message.
>
> Thank you for the patch.
>
> I already discussed a very similar patch with one of your colleagues, I
> believe.  We concluded that the pre-receive hook and the commit history
> in the commit message did not achieve its intended purposes, once you
> think carefully about exactly what is trusting what.
>
> Could you explain how your patch is different, and how it overcomes
> those difficulties, please?
>
> > Furthermore it adds information to the README about the additional
> > functionality
> > and other things that were unclear to us.
>
> If you could prepare these as separate patch(es) we can get them applied
> in parallel with the above discussion.
>
> --
> Sean Whitton
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.chiark.greenend.org.uk/pipermail/sgo-software-discuss/attachments/20220920/f00065bd/attachment.htm>