RFC - adding more info commits in verbose mode

[Marcus Lindblom]

Douglas Philips wrote:
> On 2009 Apr 14, at 10:29 AM, Marcus Lindblom wrote:
>> Ok. But I find this pretty useful to have always, and not have to  
>> enable
>> on every computer I'm working on (it's at least three).
> ...
>> Am I alone in that, or do you think this has some merit?
> 
> I don't particularly want to see it, but that's just me.

Even in -v mode?

> I think the real issue has to do with hook propigation.

Not sure if that is the real issue. I just like to have some more info 
on my commits that than I currently get. Verbose isn't not verbose 
enough, or rather, verbose in the wrong way. Therefore my proposal to 
print # of added/removed/changed lines/files.

> Yes, I know, "oooo, scary, you can't trust the other end not put a  
> nasty hook in their repo and screw you when you clone from it."

> But there are use-cases where that isn't true.
> Maybe a clone-plus command is needed, I'm not sure.

Not a bad idea. It'd simplify "corporate" adoption as it would be easier 
to enforce (or at least default-enable) useful hooks that avoid silly 
mistakes in commits that we disallow when pushing.

By marking some server hooks as 'propagate-to-client' and asking the 
user if it's ok (accept by cmd-line opt or interactive query) it could 
work pretty well.

> What I am sure of is that having to use some external-to-hg tool to  
> manage clones would be a lose.

Quite right.

Cheers
/Marcus