{"thread":{"id":"55007","subject":"Re: DEVEL: Help with feature implementation","startedAt":"2021-01-19T08:37:58Z","lastAt":"2021-01-19T08:37:58Z","messageCount":1,"participants":["Aiyee Bee"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"414676","messageId":"C8MVAN3DSJM3.PZ62BIW44K0Q@localhost","threadId":"55007","inReplyTo":null,"subject":"Re: DEVEL: Help with feature implementation","fromName":"Aiyee Bee","fromEmail":"shane.880088.supw@gmail.com","sentAt":"2021-01-19T04:58:40Z","receivedAt":"2021-01-19T08:37:58Z","isPatch":false,"sender":{"key":"shane.880088.supw@gmail.com","avatar":null},"body":"Hi Derrick and Junio!\n\nThanks for confirming my suspicions, that there isn't existing apparatus\nfor doing this, and a new bit can be added as a flag. Thanks for the\n*pointers, I'll try working it out! With Antonio, in fact, since they'd\nneed the same thing for implementing the opposite feature.\n\nAs for the justification, to elaborate on what I said in the opening mail:\n\nThis option would be pretty useful when used with diff options, to see how\nmuch two forks have diverged. I recently wanted to compare two long-running\nforks of a project and see how far they have diverged. I used the options:\n--simplufy-by-decoration --decorate-refs=\"refs/remotes/*/main\" -p\n\nBut currently with this history simplification, the diffs for both divergent\nhistories will be created against the last \"relevant\" (decorated) commit\ninstead of the last common ancestor, which creates pretty useless diffs with\na lot of intersection between them.\n\nYou're right that the option doesn't sound very useful when thought of in\nregards to history limiting by path, but IMO it's pretty useful in cases\nlike these, when you use simplify to get an 'overview' of the history.\n\nAlso sorry for the blank/duplicate emails everyone! My email client seems to\nbe misbehaving, largely because I tried to tinker with it :P\n\n- Aiyee Bee\n"}]}