Post #2349223

@b0rk@social.jvns.ca Hmm, are those extra fields stored in the commit itself or can arbitrary metadata be stored in Git? For some context (and it might have been experimented on already), Mercurial has an extension called evolve that is providing "obsolescence markers", which are pushed (and pulled) in the remote repository. Those obsolescence markers let you know when a commit was rewritten in history, e.g. after a rebase or after modifying it, and this is used to automatically "evolve" a branch modified by your peers (and also for the server to forbid pushing outdated changes, like with force-with-lease). I'm wondering if evolve could be ported to Git.