search

dcorking / codeswarm

Automatically exported from code.google.com/p/codeswarm
GNU General Public License v3.0
2 stars 1 forks source link

CVS log parsing #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Converting a CVS log to xml file

I've started using this today, but I had to change manually
convert_logs/convert_logs.py to make the xml, the problem as date parsing.

I'm from a Debian Lenny, on SVN HEAD of code_swarm.

The little changes I've made are at attached file.

Original issue reported on code.google.com by marvi...@gmail.com on 20 Jul 2008 at 7:11

Attachments:

GoogleCodeExporter commented 9 years ago 
This patch does not covert logs from TortiseCVS.  The date format I have when I 
run
cvs log is YYYY/MM/DD HH:MM:SS, not YYYY-MM-DD as you have in the patch.  When I
changed your patch to use / instead of -, it produced identical output to the
original source.  Would be better to just have the script check for dashes in 
the
input and convert them to / instead.

Original comment by nawglan on 22 Jul 2008 at 2:33

GoogleCodeExporter commented 9 years ago

Original comment by nawglan on 22 Jul 2008 at 2:35