You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(10) |
Sep
(48) |
Oct
(7) |
Nov
(16) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(27) |
Feb
(4) |
Mar
(6) |
Apr
(9) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
(1) |
2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
|
|
1
|
2
|
3
(2) |
4
(3) |
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
(1) |
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
|
|
|
From: Paul V. <pau...@gm...> - 2008-03-20 06:57:49
|
Hi, This site appears to be down for the last 2 days. Cheers, Paul. |
From: Paul V. <pau...@gm...> - 2008-03-04 20:31:55
|
Hi, As said before I'm playing with the per-directory charts and I found something I'd like some explanation for/clarification on. It seems that we only store commits in the Logcategory table that actually have files with a directory identifier "/". I have however several files in my git tree (Wine) with commits on the root level: [paul@latitude wine-git]$ git diff-tree -r --no-commit-id -M f13ef6b898cd79682a05cf8239fcfc886049e2e5 14991a42d1d28ae114f8f06f5e3ca209aefd87a7 :100644 100644 c87ab7a5ff5df54dc22d3aab8a2b799322df54db 204a2963e1ad6ca7215f3e37e40abd80ef1d3832 M ANNOUNCE :100644 100644 b1cfd817b39eb7a13ea8a87526f0c1bbd89963a2 235288c60dbfbceefb4b48f416ee5809c9fd8e39 M ChangeLog :100644 100644 fcc5388c8b6583836111ad4586d1ca32ae4240a5 872023514a432579b33f369a77e47a4a4208612b M VERSION :100755 100755 87b658ccb84ed0961bec999f9d009ed9904f3a50 9e0334865037c8d8f4157a1a236aa2be8e30c223 M configure These commits to the shown files are not available in the Logcategory table. Is this done on purpose? Line 225 in gitstat.pl shows that we start with an index of 1 meaning we skip files in the root directory. Cheers, Paul. |
From: Paul V. <pau...@gm...> - 2008-03-04 07:47:18
|
Lee jungseung wrote: > Hi, Paul > > Nice arrangement for our TODO! > > I saw Greg KH's mail at kenreltrap.org, it contains some category like you > mentioned. > > Turns out that as of 2.6.24-rc8 for the 2.6.24 kernel release we did: > lines added per day: 4945 > lines removed per day: 2006 > lines modified per day: 1702 > http://kerneltrap.org/Linux/Kernel_Rate_of_Change > > There has been no such statistics, so just like information (restrictive at > specific kernel version) are useful. I think both his and yours are > valuable. > > And.. Actually, we need clearer TODO list with timeline. > But it is not easy to make a plan and decision. ;-< > Let's talk about it later. > > Thanks, But even Linus has to do stuff by himself: http://lwn.net/Articles/270658/ Linux 2.6.25-rc3: 2.5% arch/h8300/ 13.9% arch/mips/configs/ 14.6% arch/mips/ 6.7% arch/powerpc/configs/ 7.5% arch/powerpc/ 2.5% arch/x86/ 6.1% arch/xtensa/kernel/ 6.2% arch/xtensa/ 37.0% arch/ 3.5% drivers/ata/ 6.0% drivers/hwmon/ 2.3% drivers/media/radio/ 6.1% drivers/media/video/ 9.0% drivers/media/ 3.1% drivers/net/ 13.0% drivers/scsi/ 5.1% drivers/watchdog/ 47.6% drivers/ 2.4% fs/ 2.9% include/asm-xtensa/ 5.1% include/ 2.0% net/ This is obviously something we already (more-or-less) have. Maybe that way of presenting is nicer? Cheers, Paul. |
From: Lee j. <jun...@gm...> - 2008-03-04 01:11:34
|
Hi, Paul Nice arrangement for our TODO! I saw Greg KH's mail at kenreltrap.org, it contains some category like you mentioned. Turns out that as of 2.6.24-rc8 for the 2.6.24 kernel release we did: lines added per day: 4945 lines removed per day: 2006 lines modified per day: 1702 http://kerneltrap.org/Linux/Kernel_Rate_of_Change There has been no such statistics, so just like information (restrictive at specific kernel version) are useful. I think both his and yours are valuable. And.. Actually, we need clearer TODO list with timeline. But it is not easy to make a plan and decision. ;-< Let's talk about it later. Thanks, -----Original Message----- From: git...@li... [mailto:gitstat-devel- bo...@li...] On Behalf Of Paul Vriens Sent: Monday, March 03, 2008 4:23 PM To: git...@li... Subject: Re: [Gitstat-devel] Fixed a nice bug in chart.php Lee jungseung wrote: > Hi, Paul > > I saw your commit on gitstat. > I has following up your works on gitstat! :) > Thanks, > Hi Lee, I'm now busy with the 'Per-directory changeset' chart. It's a lot of code that can be simplified greatly. Another thing is that this code has a few bugs as well :-). Next things I'm going to do: - Fix 'Per-directory changeset (Date)' - Move 'Per-direcory changeset (Date)' to libgather.php - Introduce 'Per-directory changes (Release)' - Use 'Per-directory changes (Release)' in chart.php - Introduce installation.php - Release 0.5 After 0.5: - Do more abstraction work to get all MySQL stuff to include files - Group functions together in libgather.php if possible. - Start being more object oriented as far a data gathering is concerned - Introduce a few more chart types - Release 0.5.1 I want the above release to be fairly quickly after 0.5 so people actually see something changing. Most of the work until now has been 'behind the scenes'. After 0.5.1: - Move the chart data generation (chart.php/index.php using libgather.php of course) directly to the chart generating php's. This means we don't pass data as we do now but rather specify something like "charttype=author_by_release&release=???". This would solve the problems we have with passing huge amount of data and gets rid of those awfully long links. - The rest of the TODO list :-) One thing I see when browsing the web searching for gitstat (or related stuff) is that people seem to be very interested in things like: - number of lines changed in a release - number of files changed in a release One thing I'm interested in is: - number of commits for 1 particular user over the total project (per release/date). This is an easy one I think so I may throw that in 0.5 or 0.5.1. We should also start having a clearer TODO list maybe even with timelines (ouch) ? Any other idea, remarks, suggestions? I want 0.5 to come out soon so if suggestions are simple we can do that for 0.5 otherwise it has to wait. Cheers, Paul. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Gitstat-devel mailing list Git...@li... https://lists.sourceforge.net/lists/listinfo/gitstat-devel |
From: Paul V. <pau...@gm...> - 2008-03-03 07:23:18
|
Lee jungseung wrote: > Hi, Paul > > I saw your commit on gitstat. > I has following up your works on gitstat! :) > Thanks, > Hi Lee, I'm now busy with the 'Per-directory changeset' chart. It's a lot of code that can be simplified greatly. Another thing is that this code has a few bugs as well :-). Next things I'm going to do: - Fix 'Per-directory changeset (Date)' - Move 'Per-direcory changeset (Date)' to libgather.php - Introduce 'Per-directory changes (Release)' - Use 'Per-directory changes (Release)' in chart.php - Introduce installation.php - Release 0.5 After 0.5: - Do more abstraction work to get all MySQL stuff to include files - Group functions together in libgather.php if possible. - Start being more object oriented as far a data gathering is concerned - Introduce a few more chart types - Release 0.5.1 I want the above release to be fairly quickly after 0.5 so people actually see something changing. Most of the work until now has been 'behind the scenes'. After 0.5.1: - Move the chart data generation (chart.php/index.php using libgather.php of course) directly to the chart generating php's. This means we don't pass data as we do now but rather specify something like "charttype=author_by_release&release=???". This would solve the problems we have with passing huge amount of data and gets rid of those awfully long links. - The rest of the TODO list :-) One thing I see when browsing the web searching for gitstat (or related stuff) is that people seem to be very interested in things like: - number of lines changed in a release - number of files changed in a release One thing I'm interested in is: - number of commits for 1 particular user over the total project (per release/date). This is an easy one I think so I may throw that in 0.5 or 0.5.1. We should also start having a clearer TODO list maybe even with timelines (ouch) ? Any other idea, remarks, suggestions? I want 0.5 to come out soon so if suggestions are simple we can do that for 0.5 otherwise it has to wait. Cheers, Paul. |
From: Lee j. <jun...@gm...> - 2008-03-03 06:56:07
|
Hi, Paul I saw your commit on gitstat. I has following up your works on gitstat! :) Thanks, -----Original Message----- From: git...@li... [mailto:gitstat-devel- bo...@li...] On Behalf Of Paul Vriens Sent: Friday, February 29, 2008 4:53 AM To: git...@li... Subject: [Gitstat-devel] Fixed a nice bug in chart.php Hi, I was playing with the "Top contributor's domain (Date)" charts. 2008 was selected and I could see month 1 and 2 in the month list. If you now select 2007 you will see that the month list has 1...12 plus the old 1 and 2. Likewise if you start and have 2008 in the year list you will have 1 and 2 in the month list. If you now select 1 in the month list and check the month list again it will contain 1 2 and 1 2. Just wanted to let you know that I'm still active :-) Cheers, Paul. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Gitstat-devel mailing list Git...@li... https://lists.sourceforge.net/lists/listinfo/gitstat-devel |