I love github and use it both personally and professional, however, I have mixed feelings about moving this to GIT.   I dont know if MH can survive anymore fragmentation.   

Marc has done a wonderful job of keeping a working version going and having a single official SVN repository makes that easier.   Github is going to enable all sorts of interesting development, but with the lack of any sort of standards and unit testing in the code base I doubt any of the branches will be of any greater success than the one Marc is maintaining.  

My 2 cent advice would be to focus some effort on determining what the core functionality is, get some unit tests to cover it, and deprecate the other code before moving it to yet another repository.

-J


On Wed, Oct 31, 2012 at 8:19 AM, Lieven Hollevoet <lieven@lika.be> wrote:
Hello John,


Op 31-okt.-2012, om 12:36 heeft John <john@tonebridge.com> het volgende geschreven:

> On 10/31/12 05:13, Lieven Hollevoet wrote:
>
> [snip]
>
>> You can clone the git repository without creating an account and you can use the versioning system on your own system if you want to do that. If you want to share changes, you should indeed create a github account. In that case, just login to your account, surf to the MH repository I linked above and press the 'clone' button. This will create a clone of the repo in your own account that you can work on.
>
> [snip]
>
> Can you steps to clone?  I see how to clone to my local repository:
>

Yes, a typo from my side. I meant 'fork' indeed.

How to use branches: just clone your own repository to a local drive.

> git clone git@github.com:<username>/misterhouse.git

This checks out your master branch as a default, if you want the insteon branch, first get it from the remote repo

> git checkout origin/insteon

And then apply it on your local working copy so you can work on it

> git checkout -b insteon

Switching between master and insteon is simply done with
> git checkout master
or
> git checkout insteon

Creating a new branch from your changes: set your working copy to be in the branch you want to start from, and then do

> git branch <some_descriptive_name>
> git checkout <some_descriptive_name>

And you're all set. Modify, stage, commit, test, iterate, and when done push to origin. Then create the pull request and everything is ready for merging in the main repo.

Kind regards,
 Lieven.


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365




--
Jason Sharpee
jason@sharpee.com

5929 Graburn's Ford Dr,
Charlotte, NC 28269
704-405-5893