5 ms·
Why do merge tools pretend that "their" and "our" or "remote" and "local" are good labels? Can they not show the commit message and hash? Nowadays with history
by pjtr 7y ago
Why do merge tools pretend that "their" and "our" or "remote" and "local" are good labels? Can they not show the commit message and hash? Nowadays with history editing often both sides are local and mine.
- frizkie 7y agoAnd then they get misspelled as "their's" and "our's".
- jmiserez 7y agoDid you see the screenshots? Looks like it shows the branches at least.
- pjtr 7y agoI did see the screenshots. That's what triggered my comment. I did not see any branch names. Now I see "nh-scroll-fix" and "origin/fix-simulate-na..." in the conflict dialog, but not in the merge dialog. Branch names seem insufficient anyway though, but it would be a slight improvement I guess.
- adrianmsmith 7y agoAnd, on the command-line at least, "theirs" and "ours" are reversed (only) for "rebase" [1] so that means, at least for me, I have to mentally ask myself "are theirs/ours reversed for this command?" for every command I execute, they might as well be called "foo" and "bar" at this point for me. [1] https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---merge https://git-scm.com/docs/git-rebase#Documentation/git-rebase...