[Loopdub-devel] git (was: Synchronizing MIDI controls with LoopDub)

[Stephen S. <rad...@gm...>]

> P.S.: The attached patch was made against LoopDub 0.3, not against the
> latest git. Is that an issue? The previous patch was, as well. I ask
> now only because this patch is far more invasive than the previous
> one.

I think it would be a good idea.
I'm still somewhat learning git, but I've been getting into it a lot
lately and I find it makes for a nice development environment.  I
don't know what your experience with it is so far, but it essentially
just automates a lot of what you have to do manually when you don't
use it.  Generating diffs, synchronizing your version with
development, creating testing branches, etc.  It can even help with
mailing your patches to the list.

Just because I have a set coming up (new year's!) I've finally gotten
out of this two-year slump and put a bit of work into loopdub.  So
even after the 0.3 release, I've made several commits.  Therefore, the
last couple patches you sent, I've basically made temporary branches
off of 0.3, applied the patches, done some testing, and then moved
back to the master branch and merged the branch.  Seems to work quite
well, but it would be even less work if you were working off the top
of master.  (The last one I had to do some manual merging)

Also, if you were to put up your own git repo somewhere, I could pull
changes from you directly instead of going through the mailing list.

(We could work something out with sourceforge even, if you don't have
a server... unfortunately sourceforge doesn't have git installed, but
it actually doesn't matter since git can be used over non-git-aware
transports.  It only makes pushing slightly more annoying, but for
myself I set up a post-update hook in my repo that updates the
web-hosted repo automatically when I push to it.)


Steve