`git replace`

Open cgwalters opened this issue 10 years ago • 2 comments

How does git-evtag fit into this? Does libgit2 even know about them? Offhand it seems like we should ignore them.

Aug 05 '15 21:08 cgwalters

See original https://github.com/cgwalters/git-evtag/issues/5

Aug 05 '15 22:08 cgwalters

No ignoring it is not the right thing to do because it rewrites history. The point of signing a GIT commit is to authenticate history to future consumers so the fact that history was 'tampered with deliberately' needs to be preserved in the signature because it is possible to alter the exact semantics/content of the commit.

I think what you need is a way to find out if a commit was replaced, and then sign both the original and the replace commit and do this for each commit in the history that you sign.

Dec 21 '15 17:12 cmacq2