pub enum Resolution {
SourceLocationAffectedByRename {
final_location: BString,
},
OursModifiedTheirsRenamedAndChangedThenRename {
merged_mode: Option<EntryMode>,
merged_blob: Option<ContentMerge>,
final_location: Option<BString>,
},
OursModifiedTheirsModifiedThenBlobContentMerge {
merged_blob: ContentMerge,
},
}
Expand description
Describes of a conflict involving our change and their change was specifically resolved.
Note that all resolutions are side-agnostic, so ours could also have been theirs and vice versa. Also note that symlink merges are always done via binary merge, using the same logic.
Variants§
SourceLocationAffectedByRename
ours had a renamed directory and theirs made a change in the now renamed directory. We moved that change into its location.
Fields
OursModifiedTheirsRenamedAndChangedThenRename
ours was a modified blob and theirs renamed that blob.
We moved the changed blob from ours to its new location, and merged it successfully.
If this is a copy
, the source of the copy was set to be the changed blob as well so both match.
Fields
merged_mode: Option<EntryMode>
If one side added the executable bit, we always add it in the merged result.
merged_blob: Option<ContentMerge>
If Some(…)
, the content of the involved blob had to be merged.
OursModifiedTheirsModifiedThenBlobContentMerge
ours and theirs carried changes and where content-merged.
Note that ours and theirs may also be rewrites with the same destination and mode, or additions.
Fields
merged_blob: ContentMerge
The outcome of the content merge.
Trait Implementations§
Source§impl Clone for Resolution
impl Clone for Resolution
Source§fn clone(&self) -> Resolution
fn clone(&self) -> Resolution
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more