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

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

> Okay, I will work off of master from now on.

Cool. :)

> Hmm... I'll look into it. That may be more git than I'm ready to learn
> right off the bat, so I'll start with just working off of the master
> git repo. If I'm in it for the long haul, though, it's probably the
> thing to do.

Fair enough.  I've found that it's a worthwhile tool to learn..
These MIDI code changes are a good example; we can both implement
various competing solutions and easily import each others' code to try
things out and compare.

In any case, if you just want to use it in a simple way, git-clone,
git-pull, and git-diff are probably the only commands you need.  If
you want to commit changes, try making a branch off of master to make
commits to.  Whenever you synchronize master (git-pull), you can
git-diff between your branch and mine.

> Actually, I'm just going on my experience with svn (I don't know how
> git works), but wouldn't it be possible to simply give me write
> permissions on the master git repository? Wouldn't that be a simpler
> solution? Am I simply confused?

Well, I guess I have a head start on you since I've been teaching
myself for the past few months.  I was using subversion before that,
but I like git a lot.  It gives developers a lot more freedom to do
what they want and exchange ideas without needing to do things like
giving someone else write access to your repository.

So the whole point is we can each have a repo, which live
independently, but can be synchronized in an organized way.  In a
bigger project, yes, several devs might have push access to the main
repo, but with only two programmers there's no point.  I can just pull
from you and stick it in a branch, and then merge what I want into the
master.


> I have access to a server, so that's not an issue.

Cool.  I may as well mention that there's also free git hosting
available at repo.or.cz.


cheers,
Steve