jj-vcs
docs: improve interdiff command documentation
Rewrite the interdiff help text to be clearer about what the command does
Closes #7033
I'm very open to suggestions here; I like this, but I also struggled a bit with trying to figure out how to best articulate this, especially given how overloaded every term is here. I decided to try and focus on "change" mostly, and then avoid using that word in other senses as well.
Checklist
If applicable:
- [ ] I have updated
CHANGELOG.md - [x] I have updated the documentation (
README.md,docs/,demos/) - [ ] I have updated the config schema (
cli/src/config-schema.json) - [ ] I have added/updated tests to cover my changes
Thank you. This is much better, however, I had to read the main line several times to understand it, probably because the double use of diff and not knowing the internals.
Show differences between the diffs of two changes
One question your example brings up is:
if you have a feature implemented in change A and a different way in change B, wouldn't they already have the same parent? And if they didn't, wouldn't rebasing it lose some of the change? I ask this because this command only takes single revisions, and there was a recent question about how to do interdiff for a revset that is a range that was rebased. The explanation he gave for why you don't just use the end change is that then there are other changes added or lost (because of the rebase).
Now I'm not asking to explain all that, but the example doesn't really make sense if you really think through it (at least how I thought through it, which might have bugs).
