hi all,
in the last year (or so), i have changed my personal development workflow over the last year or so, to almost exclusively use git as the version control system. Gem development has been done in git as well, with only an occasional push to the SVN repository.
this has somehow worked, but it left lots of things to be desired, and left me with a number of problems (most recently a branching/tagging dance for the 0.93 releases).
git has a number of really nice features that i use, most prominently that i can commit unstable code and only push it to the main development branch once it is finished, but still keeping all the commit history. another nice feature is, that i can work at home (where i don't have internet) and still commit regularily. it's quite easy to simlutaneously try things out on multiple machines, without polluting the public repository. branching and merging is trivial. patches by 3rd party (e.g.: you!) can keep the full authorship and log information.
and finding regression bugs is made super easy by tools like "git bisect".
given that i am the one who writes most to the repository, i did not raise a real discussion about this topic but rather silently decided to officially switch from subversion to git.
in the future i will try to not update the SVN anymore, and instead only work in git. if you want to track my changes (or commit yourself), please use these URLs
read only: git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem read/write ssh://USER@pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem
(with USER being your sourceforge username)
i hope this is fine for everybody.
gfmasdr IOhannes
hello,
ok, i'll have to learn Git... but what about the extrenal reference to Gem svn in pd externals svn?
cyrille
Le 28/08/2011 17:59, IOhannes zmölnig a écrit :
hi all,
in the last year (or so), i have changed my personal development workflow over the last year or so, to almost exclusively use git as the version control system. Gem development has been done in git as well, with only an occasional push to the SVN repository.
this has somehow worked, but it left lots of things to be desired, and left me with a number of problems (most recently a branching/tagging dance for the 0.93 releases).
git has a number of really nice features that i use, most prominently that i can commit unstable code and only push it to the main development branch once it is finished, but still keeping all the commit history. another nice feature is, that i can work at home (where i don't have internet) and still commit regularily. it's quite easy to simlutaneously try things out on multiple machines, without polluting the public repository. branching and merging is trivial. patches by 3rd party (e.g.: you!) can keep the full authorship and log information.
and finding regression bugs is made super easy by tools like "git bisect".
given that i am the one who writes most to the repository, i did not raise a real discussion about this topic but rather silently decided to officially switch from subversion to git.
in the future i will try to not update the SVN anymore, and instead only work in git. if you want to track my changes (or commit yourself), please use these URLs
read only: git://pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem read/write ssh://USER@pd-gem.git.sourceforge.net/gitroot/pd-gem/Gem
(with USER being your sourceforge username)
i hope this is fine for everybody.
gfmasdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On 08/28/2011 07:45 PM, cyrille henry wrote:
hello,
ok, i'll have to learn Git...
right. it's not that hard, once yougot used to it.
but what about the extrenal reference to Gem svn in pd externals svn?
this is something most relevant for hans. given that both pd and pd-extended (the core part, without externals) are now maintained in git, this should be managable.
fgmasdr IOhannes
On Aug 28, 2011, at 2:00 PM, IOhannes zmölnig wrote:
On 08/28/2011 07:45 PM, cyrille henry wrote:
hello,
ok, i'll have to learn Git...
right. it's not that hard, once yougot used to it.
but what about the extrenal reference to Gem svn in pd externals svn?
this is something most relevant for hans. given that both pd and pd-extended (the core part, without externals) are now maintained in git, this should be managable.
I'm fine with gem switching to git. As for removing the svn- externals, that means I'll just import the latest gem release into the pd-extended branch when I am doing a release. So if someone wants nightly builds of Gem, they'll need to set up them up. It also means that I'll likely be less active working on Gem since I don't actually use it, and really only work on getting it nicely integrated in Pd- extended.
.hc
----------------------------------------------------------------------------
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.