[PATCH 0 of 4] Add mechanisme for extension to extend default changeset log format.

[Pierre-Yves David]

On Tue, Jun 14, 2011 at 07:10:08PM -0500, Matt Mackall wrote:
> On Tue, 2011-06-14 at 01:37 +0200, Pierre-Yves David wrote:
> > * hookable default log (to ease display of state)
> > 
> >     Patches discussed in this thread. I was supprise to have no easy was to
> >     display additional information in default log.
> 
> I'm not really keen on this. If we stick in a hook, people will use it.
> And changing the default output of log is something that should be done
> with considerable caution.
> 

I understand you reticence and probably proved you right by adding all kinds of
new lines in default log.

However I still surprise that there is no way (except fragile copy/paste of the whole method) to add new
output for log. This not only hold for the vanillia default output without any
additional output. This also hold for extension that add new template keyword
but can't add flag to log to offer a simple way to display the same data.
(writing template just to add a keyword is painful and doesn't offer the same
functionnality than default output (as far as I tried))

Below is a quick list of reason I see for new line to be added to default log output

    Without any flag:

        * state (other than "published" one).
        * stamp (possible extension discussed recently on this list.
        * remoteheads (during42 extension)

        (missed opportunity)
        * bookmark (when there were not in core)
        * mq (instead of fake tag)

    With some kind of flag:

        * that changeset are hidden and/or why they are (abandon, obsolete marker).
        * first version this changeset is in (an extension I use at logilab).

        (missed opportunity)
        * transplant source
        * rebase source

-- 
Pierre-Yves David