Re: [Monotone-devel] [PATCH] parent selector 'p:xxx'
On Sun, Oct 07, 2007 at 11:54:30AM -0700, Zack Weinberg wrote: This shows the log for all revisions in a branch but does not follow merges from other branches. (tac reverses the order of lines.) It's handy for reminding oneself what was done on an old branch that has seen a couple merges from mainline since the last actual change on the branch. I'd like to spell this mtn log --no-follow-merges. Wouldn't this be --stay-on-branch or so? This will happily follow merges that happened within a branch. -- Nathaniel -- The best book on programming is still Strunk and White. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [PATCH] parent selector 'p:xxx'
Zack Weinberg wrote: On 10/6/07, Derek Scherger [EMAIL PROTECTED] wrote: On another note, I've been running a little shell script lately (coincidentally called review) that does mtn log --next 1000 --no-graph --no-merges --diffs | diffc-0.3 | less -r which shows me what I'm going to get *before* I do an update and lets me look over incoming revs. I'd be happy to call this something else though (incoming perhaps) if we use review to mean review these revs ... Ooh, I've been wondering how to do that. (What's this diffc-0.3 thing?) It's just some perl script that colorizes diffs in a way that seems to look nice. It used to be available at http://download.gnu.org/diffc-0.3 but I can't seem to get there at the moment. Also, something I've been doing a lot lately is mtn automate select b:BRANCH | mtn automate toposort -@ - | tac | while read rev; do mtn log --last 1 --no-graph --from $rev; done | less On a slightly related note I think I've seen quite a few things saying --no-graph lately and I wonder if that should really be the default? Cheers, Derek ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [PATCH] parent selector 'p:xxx'
Derek Scherger spake unto us the following wisdom: On a slightly related note I think I've seen quite a few things saying --no-graph lately and I wonder if that should really be the default? I believe that it should; if it is more than just a few columns wide, it tends to make diffs and commit messages wrap on terminals they are meant to accommodate, and it displays an unfortunate tendency to be far more than a few columns wide. Even when it is correct, for Pidgin it often has 3-5 parallel lines at two columns apiece, and often it mistakenly draws O(a lot) of parallel lines. Ethan -- The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, On Crimes and Punishments, 1764 signature.asc Description: Digital signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [PATCH] parent selector 'p:xxx'
Ethan Blanton wrote: I believe that it should; if it is more than just a few columns wide, it tends to make diffs and commit messages wrap on terminals they are meant to accommodate, and it displays an unfortunate tendency to be far more than a few columns wide. Even when it is correct, for Pidgin it often has 3-5 parallel lines at two columns apiece, and often it mistakenly draws O(a lot) of parallel lines. Another thought. Maybe what we really need is something like .csvrc where you can specify the default options that you generally want with specific commands. I'm not sure how you would occasionally un-set options that were set like this though. Cheers, Derek ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] [PATCH] parent selector 'p:xxx'
On Sun, Oct 07, 2007 at 09:58:14PM -0600, Derek Scherger wrote: Ethan Blanton wrote: I believe that it should; if it is more than just a few columns wide, it tends to make diffs and commit messages wrap on terminals they are meant to accommodate, and it displays an unfortunate tendency to be far more than a few columns wide. Even when it is correct, for Pidgin it often has 3-5 parallel lines at two columns apiece, and often it mistakenly draws O(a lot) of parallel lines. Another thought. Maybe what we really need is something like .csvrc where you can specify the default options that you generally want with specific commands. I'm not sure how you would occasionally un-set options that were set like this though. An option for this we dscussed (at the summit, I think) was a lua construct. Something that was invoked as a hook early, passed a table of the (tokenised, or partially parsed into options and their paired argument values?) command line, and given the opportunity to adjust the table before execution proceeds. Insert or remove options, modify arguments, etc etc. This would be a place where you could implement private command aliases and shortcuts, favourite branch name expansions, set or unset default options with as much context/command sensitivity as you feel like, and anything else you care to dream up. That's the basic form. Some simple way to chain these so that global, user- and workspace- specific versions could all be invoked, would also be cool. A more complex form (to implement, not for the user) would build up a table of match expressions and substitutions/actions from individual items, perhaps in a more .cvsrc-like file (a little like how .mtn-ignore is parsed and added to the hook's table). -- Dan. pgpz2IswlUhvn.pgp Description: PGP signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
