#195 added a conflict example to line_based.rs, which caused Git to be confused again #199

Closed
opened 2025-02-10 19:05:02 +01:00 by ada4a · 1 comment
Owner

This kind of highlights the fragility of the solution used in #167 (hardcoding the paths in .gitattributes). Since dealing with conflicts is the whole point of this codebase, and so conflict examples might realistically appear in any file (not to mention changes to the module structure), maybe we should just set * conflict_marker_size=15, i.e. for all files?

This kind of highlights the fragility of the solution used in #167 (hardcoding the paths in `.gitattributes`). Since dealing with conflicts is the whole point of this codebase, and so conflict examples might realistically appear in any file (not to mention changes to the module structure), maybe we should just set `* conflict_marker_size=15`, i.e. for all files?
Owner

Sure, * conflict_marker_size=15 makes sense.

Sure, `* conflict_marker_size=15` makes sense.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: mergiraf/mergiraf#199
No description provided.