monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] Re: [PATCH] mtn commit without -b and mtn branch


From: Bruce Stephens
Subject: [Monotone-devel] Re: [PATCH] mtn commit without -b and mtn branch
Date: Thu, 08 Mar 2007 21:33:50 +0000
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux)

Nathaniel Smith <address@hidden> writes:

> On Thu, Mar 08, 2007 at 06:17:15PM +0000, Bruce Stephens wrote:

[...]

>> (I haven't been paying attention to what "mtn branch" is supposed to
>> do.  I'm just dubious that it's worth making it do anything except
>> make a new branch and change the workspace to that.  But then I'm
>> dubious about the value of "clone", and I guess there's a reasonable
>> case for that (given that it'll more or less match the similarly named
>> commant in other systems).)
>
> Eh, I at least would argue that the goal is not to match other systems
> -- it's a factor, but only one of many, and not particularly high on
> the list.  The argument for clone is the same argument we hope applies
> to any UI change -- it makes life easier :-).  Just try telling
> someone "Oh, you want to get the latest source?  Okay, check this web
> page where I've written down the whole list of commands to do that,
> it's a little too complicated to explain on IRC...", the appeal of a
> single-command version will probably become obvious :-).

I guess I'm thinking that databases tend to be big enough that I want
to think about when to pull them, and where to put them.  But if and
when partial pull happens, I'd be more persuaded.

[...]





reply via email to

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