[Monotone-devel] [bug #8549] handle tree-layout merge failure sensibly

2010-05-10 Thread Stephen Leake
Update of bug #8549 (project monotone): Open/Closed: In Test = Closed ___ Reply to this item at: http://savannah.nongnu.org/bugs/?8549 ___

[Monotone-devel] [bug #8549] handle tree-layout merge failure sensibly

2010-05-09 Thread Stephen Leake
Update of bug #8549 (project monotone): Status:None = Fixed Open/Closed:Open = In Test ___ Follow-up Comment #3: This is solved by

[Monotone-devel] [bug #8549] handle tree-layout merge failure sensibly

2010-05-09 Thread Thomas Keller
Update of bug #8549 (project monotone): Assigned to:None = stephen_leake ___ Reply to this item at: http://savannah.nongnu.org/bugs/?8549 ___

[Monotone-devel] [bug #8549] handle tree-layout merge failure sensibly

2010-05-08 Thread Stephen Leake
Follow-up Comment #1, bug #8549 (project monotone): need an example; what is an unresolvable tree layout change? ___ Reply to this item at: http://savannah.nongnu.org/bugs/?8549 ___

[Monotone-devel] [bug #8549] handle tree-layout merge failure sensibly

2010-05-08 Thread Timothy Brownawell
Follow-up Comment #2, bug #8549 (project monotone): This would be for example merge(rename a to b, rename a to c) or merge(rename x to z, rename y to z) and the like. Anything that causes a merge conflict when mark-merging the parent or name of a node_t.

[Monotone-devel] [bug #8549] handle tree-layout merge failure sensibly

2010-04-30 Thread Thomas Keller
Update of bug #8549 (project monotone): Assigned to: graydon = None ___ Reply to this item at: http://savannah.nongnu.org/bugs/?8549 ___