From: Wes James <comptekki@gmail.com>
Date: Tue, 24 Aug 2010 17:53:10 GMT
Subject: Re: coding process
Message-ID: <AANLkTikXNGfFV9Bd+G4kixEzqwHLDBH0RXFHUZo5LwEu@mail.gmail.com>
In-Reply-To: <20100824172800.GA4347@localhost.localdomain>

On Tue, Aug 24, 2010 at 11:28 AM, Jared Hance <jaredhance@gmail.com> wrote:
> On Tue, Aug 24, 2010 at 09:31:21AM -0600, Wes James wrote:
>> I am working with git and I'm wondering if coding like the following
>> is a good way to manage code:
>>
>> create code then commit
>> when a good set up code is ready push to master
>> create a branch
>> create code then commit
>> when code is good, merge and push to master
>> go back to create branch
>>
>> Anyone else have a procedure they go through when managing code?
>>
>> thx,
>>
>> -wes
>
> From what you say, it sounds like you are using topic branches, which
> are always a good way to manage code. You might want to consider using
> release branches (like how git.git has "master", "next", and "maint").
>
> I'm not sure what you mean by "push to master". You don't push to a
> branch. You push to a repository. I guess you mean pushing to the
> "official" or "blessed" repository?

I meant when I do "git push origin master" - yes push to repo

> Also, sending patches to an email before merging to master is a
> good idea to get code review.

Ok.

Thx for the input.

-wes