On Sun, Jun 19, 2011 at 3:45 PM, Cor Nouws <oo...@nouenoff.nl> wrote:
> Hi *, Is there a script available, or a combination of git-commands, or ... that > is used to extract certain information for the summaries? > If so, I could use/adapt that to get information on certain weeks, > branches, ... ? > If you have a git repository then you can get info on that repo that is as fresh as your last pull. The lo-commit-stat script [Petr Mladek] in <root>/bin is capable of slicing out whatever you want. The top-dir and --log-suffix arguments are required. >From your local repo root $> cd bin $> lo-commit-stat --help # gives you the help Use the trailing git-args --since (or --after) and --before (or --until) to pick out a range of times: a last argument of --after="2011-05-31" gives bugs/bugnumbers/commits after that date to the present. Use the --bugs arg to get just the commits with associated issue numbers - the default is all commits. So, in any <repo_root>/bin directory, the command $> lo-commit-stat ../ --bugs --log-suffix='test' --after="2011-05-31" gives the list of the commits made so far this month that have an issue # in their summary as a log file in <repo_root>/bin named: bugfixes-<current_branch>-test.log Again, the list i only as recent as your latest git pull . Hope that helps, LeMoyne > Cheers, > Cor >
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
