Clarification added

This commit is contained in:
Alexandre Dulaunoy 2012-05-30 22:17:14 +02:00
parent bb11a2ad1c
commit ccf037e28c

View file

@ -1,16 +1,16 @@
gilog2timesheet
===============
gitlog2timesheet is a tool to general timesheet from git logs.
gitlog2timesheet is a tool to general timesheet from git repositories.
The hours spent per user per repository can be displayed. This can
be useful if you have to complete regular time sheet for european research
be useful if you have to complete regular timesheet for european research
project or alike.
Usage
-----
Usage: gitlog2timesheet.py path_to_git_repos
Usage: gitlog2timesheet.py path_to_git_repos path_to_git_repos...
Options:
-h, --help show this help message and exit
@ -28,7 +28,7 @@ Sample output
-------------
gitlog2timesheet.py -w 1 /home/adulau/git/forban
gitlog2timesheet.py -t -w 4 /home/adulau/git/forban
From Mon Apr 9 15:12:02 2012 to Mon Apr 9 16:12:02 2012
Alexandre Dulaunoy (a@foo.be) worked on forban
@ -45,6 +45,10 @@ Sample output
From Sun Apr 8 10:35:10 2012 to Sun Apr 8 11:35:10 2012
Alexandre Dulaunoy (a@foo.be) worked on forban
and did the following: Fixed #7 cleanup mode added
...
Forban:Philippe Teuwen->12 hours.
Forban:Alexandre Dulaunoy->964 hours.
Forban:Olaf TNSB->4 hours.
Software required
-----------------
@ -60,3 +64,10 @@ Usually assuming that a commit has an amount of time spent on it is usually wron
But the tool is usually used for organizational structure requiring timesheet in a
strict format like who did what and when. You have been warned.
Similar tools
-------------
* http://wadobo.com/trac/dtt manage time dedication per task / project using distributed version control systems.
dtt is a real tracking system when you are doing development. gitlog2timesheet objective is to avoid the burden of creating
timesheets when you have already git repositories around.