Ticket UUID: | 984d15b81114087e9ebd036b70161d1f14ea75fa | ||
Title: | Merge conflict markers could be more helpful | ||
Status: | Open | Type: | Feature_Request |
Severity: | Minor | Priority: | |
Subsystem: | Resolution: | Open | |
Last Modified: | 2010-10-15 14:11:30 | ||
Version Found In: | |||
Description & Comments: | |||
It isn't easy to understand which conflicting version is which.
CVS puts version information into markers: <<<<<<< PLIST @comment $NetBSD$ ======= @comment $NetBSD: PLIST,v 1.28 2010/09/13 12:43:16 asau Exp $ >>>>>>> 1.28meaning that the text below the opening marker is fresh, and the text above the closing marker comes from revision 1.28. It would be nice to see Fossil behaving in a similar way, e.g. putting version id and/or time stamp in conflict marker. anonymous claiming to be Joerg Sonnenberger added on 2010-10-15 13:59:32: <<<< Working copy (version: XXX) ... ==== Conflict from version YYY .... >>> End of conflict between XXX and YYY Would that break any tools for conflict resolution? anonymous added on 2010-10-15 14:11:30: Not to mention changing user habits when doing the same visually. |