A state-of-the-art survey on software merging¶
Mens, T. (2002). A state-of-the-art survey on software merging. IEEE Transactions on Software Engineering, 28(5), 449-462.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Branching and Merging
- The structural insight is robust: a code repository, a clade of organisms, a family of languages, and a set of design prototypes all exhibit the same divergence-then-reconvergence logic, and in each the merge is where the topology earns its keep — it is the only place the parallel histories are forced to confront one another.
This sourceSurvey of software merge techniques (textual, syntactic, semantic, operation-based): identifies the merge as the load-bearing reconciliation point and documents that a mechanically successful textual/structural merge can still produce a semantically incoherent result, guaranteeing only the absence of detected conflict.
- The structural insight is robust: a code repository, a clade of organisms, a family of languages, and a set of design prototypes all exhibit the same divergence-then-reconvergence logic, and in each the merge is where the topology earns its keep — it is the only place the parallel histories are forced to confront one another.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:57fced84e5e8 · see in the full table