monotone-devel
[Top][All Lists]
Advanced

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

Re: [Monotone-devel] Questions pertaining Eclipse Integration


From: Nuno Lucas
Subject: Re: [Monotone-devel] Questions pertaining Eclipse Integration
Date: Sun, 29 Oct 2006 11:44:08 +0000

On 10/29/06, Richard Levitte - VMS Whacker <address@hidden> wrote:
In message <address@hidden> on Sat, 28 Oct 2006 19:27:18 -0500, Timothy Brownawell 
<address@hidden> said:

tbrownaw> I'm not sure we want to change the default, the
tbrownaw> recursiveness is kinda nice.

Yes and no.  Yes, I love it when it does include all files *when I
want that to happen*.  Also, it's quite confusing that it work
differently from its opposite, "drop".  There are times, when I'm
tired, where I get a bit frustrated "because it doesn't work like it
used to" before I realise that I was thinking about "the other
command".  Inconsistency can be a bitch at times.

Agree with you.
I would lobby for the default to not be recursive, but the fact is
others scm's (like subversion) default to being recursive, so maybe is
what users expect.

On the other hand, I find it terribly annoying that after I do a "mtn
add *" and then do a "mtn drop *" to make it forget about my mistake
it bails out with "mtn: misuse: path '_MTN' is in bookkeeping dir".

That makes it "untrivial" to repair a mistake that is completely
harmless (as no commit was done and no files are changed).

I believe this is a side effect of renaming from the old dotted ".mtn"
name, and would consider this a bug, because if people wanted this to
happen, they would had codded this behaviour before.


Regards,
~Nuno Lucas


Cheers,
Richard




reply via email to

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