From 62db856bfe87ff893065ed0965b4346f40f261e7 Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Sat, 26 May 2012 12:11:45 +0200 Subject: [PATCH] removed README --- README | 52 ---------------------------------------------------- 1 file changed, 52 deletions(-) delete mode 100644 README diff --git a/README b/README deleted file mode 100644 index def6544..0000000 --- a/README +++ /dev/null @@ -1,52 +0,0 @@ -gilog2timesheet -=============== - -gitlog2timesheet is a tool to general timesheet from git logs. - -Usage ------ - - Usage: gitlog2timesheet.py path_to_git_repo(s) ... - - Options: - -h, --help show this help message and exit - -d, --debug output debug messages - -w COMMITFACTOR, --commitfactor=COMMITFACTOR - work time factor per commit, default is 4 hours - -Sample output -------------- - - - gitlog2timesheet.py /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 - and did the following: Fixed #12 test if loot directory exists - - From Mon Apr 9 13:30:30 2012 to Mon Apr 9 14:30:30 2012 - Alexandre Dulaunoy (a@foo.be) worked on forban - and did the following: Fixed #9 lootcleanup added - - From Mon Apr 9 12:41:42 2012 to Mon Apr 9 13:41:42 2012 - Alexandre Dulaunoy (a@foo.be) worked on forban - and did the following: Fixed #10 The browsing is now naturally sorted. - - 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 - -Software required ------------------ - -* Python 2.4 and up -* git - -Note ----- - -Usually assuming that a commit has an amount of time spent on it is usually wrong. - -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. -