Re: [Monotone-devel] log options and staying on the current branch

[Richard Levitte]

Personally, I'd find it irritating to have the history broken off just
because it went into another branch for a while...  Maybe we should
think about having a ~/.monotone/opts file to give the users a
possibility to have their own default option values or somesuch...

Either way, I'm actually writing to remind you to add something in
NEWS, even though you're working in your own branch.  Just to make
sure it's not forgotten when the time comes to propagate this back
into the main branch :-).  Could you please?

Cheers,
Richard

In message <address@hidden> on Sun, 22 Feb 2009 19:58:45 -0700, Derek Scherger 
<address@hidden> said:

derek> I've often found it mildly irritating that log doesn't normally stay on 
the
derek> current branch and that there's no nice way to specify this other than
derek> something like:
derek> 
derek> $ mtn automate select b:net.venge.monotone.library-build |mtn automate
derek> toposort address@hidden | xargs -n 1 mtn log --last 1 --diffs --from
derek> 
derek> I've "fixed" this on the branch net.venge.monotone.experiment.log-options
derek> which does this and a few other things:
derek> 
derek> 1. adds --author --branch --date and --message options to log and allows
derek> them all to take globs that will select interesting revisions
derek> 2. since --branch is a workspace option, this has the consequence that 
the
derek> default branch glob is the current workspace branch and so log now stays 
on
derek> that branch by default
derek> 3. logging all branches can be done by specifying --branch='' (the empty
derek> branch) or --branch='*' (an inclusive glob); the former will not bother
derek> attempting to match anything and will simply include any branch; the 
latter
derek> goes through the globish machinery to achieve the same thing, in a very
derek> slightly more expensive way
derek> 4. changes workspace::get_options slightly, to allow --branch='' to work;
derek> previously if the specified branch option was empty and the workspace 
branch
derek> was not the workspace option was used. I think this is incorrect, if
derek> --branch='' is specified on the command line then that should override
derek> whatever is in the workspace
derek> 
derek> There are a couple of failing tests with this that I still need to look 
into
derek> but it's a pretty simple change and I think it would be very nice to 
have.
derek> I'm curious what other people think though.
derek> 
derek> Cheers,
derek> Derek

-- 
Richard Levitte                         address@hidden
                                        http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish