summaryrefslogtreecommitdiff
path: root/gitdm
AgeCommit message (Collapse)AuthorFilesLines
2011-02-17Making the datelc an actual csv for easier data handlingCédric Bosdonnat1-2/+3
2011-02-11Why should we exit after datelc output?Cédric Bosdonnat1-1/+0
2011-02-11Only add Linus and Andrew with -aCédric Bosdonnat1-3/+4
[jc: removed unneeded global line]
2010-10-04Make tag matching stricterJonathan Corbet1-5/+5
If you commit a git changelog to your repository, gitdm will be confused by all the added patch tags. So make the patterns stricter to force them only to match within the git log metadata - or so we hope. There is still room for confusion here; we really need to make grabpatch() smart enough to split metadata and the diff. Don't have time for that now. This patch changes results slightly. In the 2.6.36 cycle, there's a tag reading: Original-Idea-and-Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org> Pre-patch gitdm would recognize that as a signoff; after the change it no longer does. Reported-by: Wolfgang Denk <wd@denx.de> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2010-06-30Add option to get the configuration files from a given base directoryTiago Vignatti1-3/+8
Instead boringly be replicating the directory base name where gitdm is installed and write it on each option inside the configuration file, just send it through the command line. Signed-off-by: Tiago Vignatti <tiago.vignatti@nokia.com>
2010-05-03Only gripe about missing author names onceJonathan Corbet1-1/+12
(per name) Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2010-02-06Move out global houskeeping from grabpatch()Martin Nordholts1-18/+19
As a step to make grabpatch() more unit-test friendly, move out global houskeeping from grabpatch(). This also gets rid of a TODO in the code. The regression tests still passes after this refactoring, of course. Signed-off-by: Martin Nordholts <martinn@src.gnome.org>
2009-07-24Get the developer count right even without full patch infoJonathan Corbet1-1/+1
2009-07-24gitdm: report issue when an email address is a "name"Greg Kroah-Hartman1-1/+5
This probably means an incorrect commit message, it also means that if it is not fixed, the category for this person is probably going to be incorrect. Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-07-24add more spaces to the "done" message so it doesn't show the trailing 0Greg Kroah-Hartman1-1/+1
2009-07-24Reduce the number of "funky email" gripesJonathan Corbet1-2/+2
Addresses of the form "user at host.wherever" can be trivially repaired, so let's do so. A couple of other minor tweaks are included here as well; nothing which changes behavior.
2009-03-21Quick hack to make the developer/employer counts at the top correctJonathan Corbet1-2/+9
...before we were counting everybody we knew about, regardless of whether they did anything in the period we're looking at.
2008-11-11Tested-by / Reported-by credits and moreJonathan Corbet1-193/+72
Add tracking of tested-by, reported-by, and reviewed-by. For the first two, we also track who is *giving* those credits. While I was in the neighborhood I also: - Started turning the "patch" class into something more than a bare container; this work has just begin. - Moved the report-writing code into its own file (reports.py)
2008-10-06gitdm patch ...Michael Meeks1-4/+13
Hi guys, I knocked up a patch to generate some per-month, by-affiliation statistics from the gitdm output; attached for interest or merging. A sample of the output, complete with OO.o data-pilot, and pretty chart is here: http://www.gnome.org/~michael/data/2008-09-29-linux-stats.ods with chart here: http://www.gnome.org/~michael/images/2008-09-29-kernel-active.png caption being: "Graph showing number and affiliation of active kernel developers (contributing more than 100 lines per month). Quick affiliation key, from bottom up: Unknown, No-Affiliation, IBM, RedHat, Novell, Intel ..." These are as yet not published, I plan to use them as a comparison to OO.o's somewhat mediocre equivalents; hope to go live with them soon (and fix the horrible bugs in stacked area charts to make them actually pretty ). HTH, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2008-09-05Don't accept totally bogus datesJonathan Corbet1-1/+4
Yanmin Zhang committed a patch (09f2724a786f76475ef2985cf84f5359c553aade) which claims to have been written in August, 2030. Code that bleeding-edge makes gitdm confused, so pretend it's just normal, contemporary stuff.
2008-07-24finally get the config file stuff correctGreg KH1-6/+6
Need to seed the database _after_ loading the config file, otherwise we don't see the seeds as actually showing up for their companies. Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2008-07-24parse the config file _after_ we have read the command line optionsGreg KH1-2/+6
Otherwise it doesn't matter if we change the config file option or not... Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2008-07-24make -c option actually workGreg Kroah-Hartman1-1/+1
The -c option was not fully implemented Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2008-07-18Fix up the copyright notices.Jonathan Corbet1-2/+2
2008-07-18Move regular expressions out to patterns.pyJonathan Corbet1-17/+2
...I need them for an associated tool I'm working on.
2008-06-27gitdm: Report progress to stderr not stdoutKir Kolyshkin1-5/+3
When gitdm is used for generating text-only report with its output redirected to a file, all is well aside from the clutter at the beginning of that file -- a very long line with repeating "Grabbing changesets...". Solve that by redirecting progress reporting to stderr. It also helps to see the progress when you redirect gitdm output to a file. Also, we don't have to flush stdout since stderr is unbuffered by default. Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
2008-06-27Initial commitJonathan Corbet1-0/+499
First commit of gitdm to the new repo. Call it version 0.10 or something silly like that.