monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Re: Is this the right mailing list? [Was: upgrading 0.3


From: Lapo Luchini
Subject: [Monotone-devel] Re: Is this the right mailing list? [Was: upgrading 0.36-0.37: "mtn: fatal: std::logic_error: roster.cc:186: invariant 'fetching nonexistent entry from children' violated"]
Date: Fri, 07 Dec 2007 10:13:14 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.0

Arthur A. Gleckler wrote:
> All is well now.
> That was a real scare!

What about the broader UI problem this exposed?

I wonder what's best:
1. don't allow commits with names that are caseless-equals to existing
ones (or allow only it with a switch that clearly states "use this only
if this project won 't EVER be used on Windows or Mac")
2. allow them perfectly at commit phase, but fail graciously on checkout
("this system is not case sensitive, and this procontains both 'a' and
'A', please rename one of the two"... and that would imply that a
"rename without checkout" would be needed, so that people can actually
"solve" the problem by themselves.... maybe considering
caseless-name-clashes a real node conflict and create a "node conflicts
editor" that interactively asks: A and B wants the same name, which one
wins, which one gets deleted? Aa and AA want to be saved, do you like to
drop/renam Aa? drop/rename AA?... and at the end of this interactive
session it just commits a merge when those choices were automatically
done, with no need to check out separately ther past revisions, fixing
them, and re-doing the now-clean merge)

  Lapo





reply via email to

[Prev in Thread] Current Thread [Next in Thread]