Rereading what I wrote, I came across as unintentionally harsh and
rude. Sorry about that - I was trying to be concise and terse, and it
went a bit wrong :)
What I was thinking to improve this is two short-term fixes:
1. Can we get git log -m -p . in the top level directory to show
the same commits as just git log -m -p ?
2. Can we get git log -m -p somefile to show all the
changes to that file? Including when lines are added and then removed
by the merge somehow?
But in the longer term, I was thinking about how this could be improved...
What if merge commits were forced into being always trivial? i.e.
prevent merges with conflicts or code changes?
Then conflict resolution and code changes are pushed into a second
"ordinary" commit. That way you can always see what changes have been
made to the code.
E.g. If you have branch "master" and branch "A", and there are
conflicts when you merge, you could end up with:
merge commit
| \
| preparation changes to fix conflicts with oldmaster
oldmaster |
A
I know this isn't great, but maybe something along these lines?
Ideally I'd like to see all the code changes to a code base just with
"git log -p".
Any thoughts?
Thanks,
John Tapsell
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
