monotone-devel
[Top][All Lists]
Advanced

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

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


From: derek
Subject: Re: [Monotone-devel] [PATCH] Make --execute default
Date: Tue, 27 Feb 2007 15:25:30 -0700
User-agent: Mutt/1.5.13 (2006-08-11)

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.

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.

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. ;)

Cheers,
Derek





reply via email to

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