Changelog parser?

[Swap]

Hi there.

I'm trying to generate a code_swarm video for Octave (http://
www.octave.org). They used to have CVS, but since have moved to
Mercurial, and I cannot find CVS-generated logs. What does appear to
be very complete is a source Changelog that goes all the way back to
1992. It has some problems, though, like entries not being in
chronological order, but it follows the Changelog format perfectly.

Before I write (and submit) a Changelog parser for code_swarm, I just
want to make sure you guys don't already have one.

Thanks,
- Jordi

[kordless]

I posted last week about using Splunk and code_swarm to visualize
other types of logs: http://wiki.splunk.com/Dev:Splunk_Swarm. I think
you should be able to take what I wrote and apply it to visualizing
the other logs.

More than happy to help if you need assistance getting it running.

Cheers,
- Kord

On Oct 11, 3:35 pm, Swap <jord...@gmail.com> wrote:
> Hi there.
>

> I'm trying to generate a code_swarm video for Octave (http://www.octave.org). They used to have CVS, but since have moved to

[Jordi Gutiérrez Hermoso]

2008/10/11 kordless <kord...@gmail.com>:

> I posted last week about using Splunk and code_swarm to visualize
> other types of logs: http://wiki.splunk.com/Dev:Splunk_Swarm. I think
> you should be able to take what I wrote and apply it to visualizing
> the other logs.

Thank you. Unfortunately, it looks like Splunk is non-free. Since I
want the Octave devs to check my work or replicate it, they won't like
this. It's also a huge binary download, probably a lot more complex
than I need for this purpose.

I can write short a Perl program to parse the Changelog and output...
what's the format? Also, you guys probably prefer Python. This is a
good opportunity for me to practice my Python to do some simple
parsing.

- Jordi G. H.

[Jordi Gutiérrez Hermoso]

2008/10/11 Jordi Gutiérrez Hermoso <jor...@gmail.com>:

> I can write short a Perl program to parse the Changelog and output...
> what's the format?

Oh, sorry, I should have looked around before I looked. The output is
a very simple XML file, nice. Hm, I'll just add the Changelog format
to convert_logs.py, send you guys a diff, and hope you like it.

- Jordi G. H.

[Sébastien Rombauts]

ooops

---------- Forwarded message ----------
From: Sébastien Rombauts <sebastien...@gmail.com>
Date: 2008/10/12
Subject: Re: [code_swarm] Re: Changelog parser?
To: Jordi Gutiérrez Hermoso <jor...@gmail.com>

Hi,

Yes, do so : addind the Changelog format would give us a nice feature.
It would be great if you could take the time to validate it with a few different changelog form different origins.

Sébastien

2008/10/12 Jordi Gutiérrez Hermoso <jor...@gmail.com>

[Jordi Gutiérrez Hermoso]

2008/10/12 Sébastien Rombauts <sebastien...@gmail.com>:

> 2008/10/12 Jordi Gutiérrez Hermoso <jor...@gmail.com>
>>

>> Hm, I'll just add the Changelog format to convert_logs.py,

> Yes, do so :

Done, see attached. I also managed to produce the following:

http://platinum.linux.pl/~jordi/movies/octave-code-swarm.avi

For some strange reason it died on me around 2004, which is a shame
since Octave development really exploded around 2007. :-(

Btw, the Changelog format is described in the GNU coding standards, here:

http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html

I am sure we can expect that other GNU member projects will adhere to
this format.

> It would be great if you could take the time to validate it with a few
> different changelog form different origins.

I tried it with the Octave Changelogs which go back to 1992 and
changed formatting more than once. Also, the Changelogs are scattered
amongst various directories; for that I manually went to each
directory, ran a quick sed on each Changelog so that all the files in
each subdirectory had that subdirectory as a prefix, catted all the
Changelogs together into one, and then ran convert_logs.py on that.

I'm not sure if this procedure should also be automated by the Python
script, recursing into subdirectories. Maybe.

Anyways, HTH
- Jordi G. H.

[Peter Burns]

Thanks for the patch, I'd never have thought of parsing changelog
files for events like that. I've committed your changes (with a bit
of refactoring to account for differences in the code base) into my
fork of code_swarm: http://github.com/rictic/code_swarm/commit/802f3da55460f9142e55d9d529acd5c897ae5394


On Oct 12, 3:39 am, "Jordi Gutiérrez Hermoso" <jord...@gmail.com>
wrote:
> 2008/10/12 Sébastien Rombauts <sebastien.romba...@gmail.com>:
>
> > 2008/10/12 Jordi Gutiérrez Hermoso <jord...@gmail.com>

>  convert_logs.py.diff
> 4KViewDownload