You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It isn't currently possible to generate a merge-file when working with bare repos. This makes it impossible to determine the conflicting parts of a given file when trying resolve a conflict during a merge. It would be lovely if there were a mechanism by which to generate a diff (or something like it) that only shows the conflicting parts of the file. This would enable the creation of user friendly merge tools without relying on parsing the merge-file from the filesystem (especially in cases where you're using bare repos and alternate ODB backends).
I don't have a proposal for the API for this feature, but I suspect it should look something like a diff.
Would anyone else find this useful? Happy to help work on it if we can rough out an API. At the very least I promise to update the Rugged bindings.
It isn't currently possible to generate a merge-file when working with bare repos. This makes it impossible to determine the conflicting parts of a given file when trying resolve a conflict during a merge. It would be lovely if there were a mechanism by which to generate a diff (or something like it) that only shows the conflicting parts of the file. This would enable the creation of user friendly merge tools without relying on parsing the merge-file from the filesystem (especially in cases where you're using bare repos and alternate ODB backends).
I don't have a proposal for the API for this feature, but I suspect it should look something like a diff.
Would anyone else find this useful? Happy to help work on it if we can rough out an API. At the very least I promise to update the Rugged bindings.
cc/ @ethomson
The text was updated successfully, but these errors were encountered: