Report Generation

[Steve Barnes]

On 29/05/14 18:20, David Wink wrote:
> I would like to produce a weekly report in the following layout.
>
> Engineer A
>
> Day 1
>
>   Pull from central repository
>
>     Commit Action 1 -- to a local repository
>
>     Commit Action 2 -- to a local repository
>
>  Push to a central repository
>
> Day 2
>
> Same basic idea
>
> Day 3
>
> Same basic idea
>
>
> Engineer B
>
> Day 1
>
>   Pull from central repository
>
>     Commit Action 1 -- to a local repository
>
>     Commit Action 2 -- to a local repository
>
>   Push to a central repository
>
> Day 2
>
> Same basic idea
>
> Day 3
>
> Same basic idea
>
>
> is there an extension that will help me pull this information?  or Can 
> I get some input on how you all would go about gathering the data for 
> this?
>
>
> Thanks in Advance.
>
>
>
>
>
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
David,

I don't think that Mercurial records the date time of pulls/pushes other 
than locally in the resulting local repository, (but of course any 
un-pushed commits will be missing),  but for the rest of your details 
you could try:

# Update your copy of the repo first!
hg pull
hg log -r "sort(date('-7'), user)"

To get closer to your exact format you can either use templates, (see hg 
help templates), or post process the results of the above.

Gadget/Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140530/bdeed374/attachment-0002.html>