Move to Git? [sf#9] about python-control

[murrayrm]

Commented by jgoppert on 2014-03-24 23:20 UTC
I started my git svn clone here on github https://github.com/jgoppert/python-control . I'll keep all of my changes on the dev branch and the svn clone on master so if I start finding more fixes I can keep them in one place and they should be easy for you to merge. I can just diff the two branches and hand you svn patches.

[murrayrm]

*Commented by anonymous on 2014-03-24 23:24 UTC
By "moving to git", perhaps you meant moving to GitHub. In terms of version control, SourceForge.net now offers Git.

In any case, you should consider providing a link back to http://python-control.sf.net/ , since the README does not include one, and your fork on GitHub may be confused for the real thing.

[murrayrm]

Commented by jgoppert on 2014-03-25 00:00 UTC
I've worked with sourceforge git repos. I just think that svn is more difficult to use than git. I will add a readme file that points users back to sourceforge. I respect sourceforge for supporting open source projects and don't mean to recommend moving away from sourceforge.

As I'm dusting off the discrete control functions I've got more patches. See patch request. Here is a link to the patch of my current changes that should continue updating: https://github.com/jgoppert/python-control/compare/master...dev.patch

[murrayrm]

Repository and issue tracker now moved to GitHub. Closing out.