I was looking to hack on a problem I'm having with pisg (it's not parsing my newer eggdrop logs despite getting the latest release) and I noticed that the Git history begins with a flat import from CVS. I was wondering if anyone tried to use cvs-fast-import or another cvs-to-git migration tool to preserve the old history? If not, is there a copy of the old CVS repo available to try? For a project with such a long history it seems worth trying if it hasn't been tried.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was looking to hack on a problem I'm having with pisg (it's not parsing
my newer eggdrop logs despite getting the latest release) and I noticed
that the Git history begins with a flat import from CVS. I was wondering if
anyone tried to use cvs-fast-import or another cvs-to-git migration tool to
preserve the old history? If not, is there a copy of the old CVS repo
available to try? For a project with such a long history it seems worth
trying if it hasn't been tried.
Maybe update this in project summary? I was stumped seeing "create ticket" disabled and then somebody on IRC pointed me towatrds github repo. Could've saved 10-15 minutes easily! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was looking to hack on a problem I'm having with pisg (it's not parsing my newer eggdrop logs despite getting the latest release) and I noticed that the Git history begins with a flat import from CVS. I was wondering if anyone tried to use cvs-fast-import or another cvs-to-git migration tool to preserve the old history? If not, is there a copy of the old CVS repo available to try? For a project with such a long history it seems worth trying if it hasn't been tried.
Oh, I had assumed people would convert the old repo to git when they
were talking about moving the project. I didn't check as I had not
committed anything for years.
It looks like the old CVS tree is not functional at the moment:
cvs update: Updating .
cvs update: failed to create lock directory for /cvsroot/pisg/pisg' (/cvsroot/pisg/pisg/#cvs.lock): Permission denied
cvs update: failed to obtain dir lock in repository/cvsroot/pisg/pisg'
Hi,
I was looking to hack on a problem I'm having with pisg (it's not parsing my newer eggdrop logs despite getting the latest release) and I noticed that the Git history begins with a flat import from CVS. I was wondering if anyone tried to use cvs-fast-import or another cvs-to-git migration tool to preserve the old history? If not, is there a copy of the old CVS repo available to try? For a project with such a long history it seems worth trying if it hasn't been tried.
Thanks!
Hey
Latest version, including all commits is here: https://github.com/PISG/pisg
2017-01-03 18:05 GMT+01:00 opello opello@users.sf.net:
I didn't even think to check Github, thanks!
Maybe update this in project summary? I was stumped seeing "create ticket" disabled and then somebody on IRC pointed me towatrds github repo. Could've saved 10-15 minutes easily! :)
Re: opello 2017-01-03 /p/pisg/discussion/general/9a05e14a69f64fb87d65c6c852e3df228af000b3.discussion@pisg.p.sourceforge.net
Oh, I had assumed people would convert the old repo to git when they
were talking about moving the project. I didn't check as I had not
committed anything for years.
It looks like the old CVS tree is not functional at the moment:
cvs update: Updating .
cvs update: failed to create lock directory for
/cvsroot/pisg/pisg' (/cvsroot/pisg/pisg/#cvs.lock): Permission denied cvs update: failed to obtain dir lock in repository/cvsroot/pisg/pisg'I don't think I have a copy of the repo around.
Christoph
Just in case you don't get an email from the other reply here, it's moved to Github:
https://github.com/pisg/pisg
Thanks!