Re: [Monotone-devel] Re: Cherry-Picking, Renames, Etc.

[Oren Ben-Kiki]

On Monday 29 November 2004 19:53, Bruce Stephens wrote:
> Why not just have the things independent of monotone?  So you run
> monotone_guess before committing, or something?

Because I'd need a separate "infrastructure" (config files, paths, 
environment variables...).

> For what it's worth, I think commit ought to work from a specially
> formatted file, which would include the log and list the files to
> change.  So you'd use "monotone prepare" or something...
>
> That would more naturally separate out the process of deciding what's
> changed and actually committing it

Sounds like a promising approach.

> More philosophically, it would return control to me.  Right now
> commit drives everything: it decides what files it thinks need to be
> committed, it throws me into an editor to construct the long log
> message.  (It's no different to other systems in this respect as far
> as I know, and normally this is what you want, but I'd like a
> user-driven alternative sometimes.)

Actually, most other systems allow you to specify that you only commit 
some of the files.

Have fun,

 Oren Ben-Kiki