Re: [Monotone-devel] Re: CMD_NO_WORKSPACE(checkout)?

[Stephen Leake]

Lapo Luchini <address@hidden> writes:

> Thomas Keller wrote:
>>   $ mtn check  # I meant `make check`
>
> Oh… wow! that would really be unexpected.
> (but not dangerous, fortunately, only… slow and unexpected)

I agree avoiding unexpected behavior is good.

>> While it may be useful to have other defaults read from there, f.e. the
>> database file path or the key directory
>
> Uh, yes… just saturday I did
> $ mtn co net.venge.monotone.stripped ../stripped
> as a shortcut instead of writing the full options…

Maybe a warning/error if the new checkout is in an existing workspace?
I don't think there's any real use case for that.

>> rather like to see checkout acting explicitely on the user's input, i.e.
>> by prompting him to give it a --revision or --branch option.
>
> I think making one of those two mandatory would be nice, but didn't you
> say it was too late to know if that was on the command line or no?
> ;)

perhaps we need to enhance the options interface with an origin field?

-- 
-- Stephe