On Thu, 19 Aug 2021 00:23:26 -0400 Christopher Speck <die.drac...@gmail.com> wrote:
> The commit message cannot be modified to include additional noise for the > case I'm working on. I'm not familiar with extras, but that might be a way > to work around this. Does that require any further extension to be enabled > beyond evolve? I tried `hg help --keyword extras` and it indicates a > `commitextras` extension allows this. Basically, 'extra' is a field in hg's storage that can store arbitrary data from commands and extensions that will affect the hash. It's internal to hg commands, meaning that there's usually no way to set/change what it stores with any flags from CLI. commitextras is an extension that simply adds --extra flag to hg commit, so that people with specific needs could add extra data to commits from CLI. What you need is to add this flag to hg rebase, and then use it in your tool. This probably means writing your own extension based on commitextras or maybe extending it to also augment hg rebase command with --extra flag. Sorry it couldn't be easier, but since you want something opposite of what hg does internally by default, this is, in my opinion, the easiest way to achieve it right now. You can also try asking this question on mercurial-devel mailing list to get more eyes on it. It's possible that no one previously thought of your use case and rebase could be made to add extra noise to produce new hashes every time in the next release of hg. But this way you'll have to wait for the release and you'll be tied to that hg version at minimum. https://www.mercurial-scm.org/wiki/MailingLists _______________________________________________ Evolve-testers mailing list Evolve-testers@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/evolve-testers
