- Appended to comment:
drh added on 2009-03-21 16:24:43:
Fixed in 83566f24241a01bedbf89d8ca068c7c1b926b4f0 - Change resolution to "Fixed"
- Change status to "Fixed"
- Appended to comment:
anonymous added on 2009-03-11 07:24:03:
This is pretty atrocious, to be honest. I cannot think of any tool that does this bad a job at handling merge conflicts, period. Even diff/patch .rej files are superior. - Change resolution to "Open"
- Change severity to "Severe"
- Change comment to "It would be nice if the conflict markers in merge results looked like: <verbatim> >>>>>>>> BEGIN MERGE CONFLICT <<<<<<<< <my version> ====================================== <your version> >>>>>>>>> END MERGE CONFLICT <<<<<<<<< </verbatim> Sometimes it's not clear where one parts ends an another one starts, especially when merging branches after the development has diverged for a while."
- Change foundin to "bc857ecd92"
- Change private_contact to "6984f5ff2d3f66a87d3c6ddcf777c37b54e478f0"
- Change severity to "Minor"
- Change status to "Open"
- Change title to "Confusing conflict markers"
- Change type to "Feature_Request"