Re: [Monotone-devel] [PATCH] Make --execute default

[William Uther]

On 28/02/2007, at 9:25 AM, address@hidden wrote:

> On Wed, Feb 28, 2007 at 12:08:34AM +1100, William Uther wrote:
> > More extensive tests have gone in to the branch.  If there are no
> > objections, I'll merge this into trunk tomorrow sometime.
>
> I'm going to take the other side of this whole thread for a minute. I
> personally don't really have a problem with the current, don't do
> anything, behaviour.
>
> The one oddity I note is that "mtn add foo" does not create anything
> called "foo" but simply notes that it should be added and if we make
> rename and drop (aka remove) do things then there's an (albeit minor)
> inconsistency.

I was thinking of making --bookkeep-only the default for 'drop' and -- 
execute the default for 'remove'.  That would leave us with two  
options though, and I wasn't sure it was worth it.

> Another approach would be to come up with something like ~/.cvsrc  
> where
> you can add various options to commands that you generally want.  
> Then if
> you want --execute on some commands *you* can have it and I can opt  
> out.

Heh.  This was what I first suggested.  I was then told that it would be
better to just get the default right and make it so people don't want to
change it (which I agree with).

> As far as the {pull,sync,merge}+update and other command combinations
> that have also been talked about, these could potentially be  
> handled with
> a persistent --update option to pull,sync,merge that can be set as
> people prefer.
>
> On the other hand, I don't object to making --execute the default very
> strongly either and we could do that and see how it goes for a  
> while. ;)

Which I've done.  I assume people will complain if they don't like it.

I personally think it is a little chatty still.  But it is probably  
better to be too chatty than not chatty enough - at least to start.

Be well,

Will       :-}