Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.37 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Fri, 22 Mar 2013 09:41:14 -0700
Subject: Re: [OT] Log history
Thread-Topic: [OT] Log history
Thread-Index: Ac4nFLbHRxAuvXMlSdi9XrswS2IzzgAB1pVF
Message-ID: <CD71D7BA.4FD45%aharui@adobe.com>
In-Reply-To: <334259FA-12A5-4BA7-9712-55C1AD00C269@adobe.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.16.0.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

AFAICT, the git branching model does not dictate that you must use a branch
for all changes to develop, it just talks about a strategy for how to use
feature branches if you choose to use them.

I'm a git newbie, but really, I am looking forward to having the option to
create a cheap and quick branch to do multi-commit changes to the code.
Quite often I get disrupted from some work I'm doing and when I come back I
find myself looking at the diffs against the SVN repo and trying to remembe=
r
why I did something.  With a local branch, I can "commit" with a record of
what I did and have local history of what I did to refer to when I come
back.  Sounds like a good thing to me,  But there is no requirement to make
a branch unless you need that sort of thing.

Regarding the rebase option.  I spent last evening reading all of the
articles Justin and other pointed us to.  It seems pretty straight forward
to me:  You should use rebase when refreshing your local branch against the
remote branch it came from before pushing.  You should not rebase when
merging between two remote branches (and therefore, I am not setting the
config to default to rebase because I will be merging remote branches when
doing releases).  And for other configurations, it is best to understand
what it really does, and if you decide to use it and it fails, abort it and
use merge.


On 3/22/13 8:48 AM, "Gordon Smith" <gosmith@adobe.com> wrote:

> I plan to do my Falcon development work on the 'develop' branch. The full=
 nvie
> model is complete overkill for what I am doing and I don't need umpteen
> feature branches. Has everyone forgotten about KISS?
>=20
> - Gordon=20
>=20
> Sent from my iPad
>=20
> On Mar 22, 2013, at 3:37 AM, "Justin Mclean" <justin@classsoftware.com> w=
rote:
>=20
>> Hi,
>>=20
>> Also anyone want to explain why this doesn't mention pull -rebase anywhe=
re?
>> http://nvie.com/posts/a-successful-git-branching-model/
>>=20
>> Also on the bug fix issue to branch or not branch (from the author of
>> gitflow):
>> "A rule of thumb would be that if you need more than one commit for a ch=
ange,
>> you should do it on a feature branch, otherwise commit it directly on
>> develop."
>>=20
>> https://github.com/nvie/gitflow/issues/24
>>=20
>> Thanks
>> Justin
>>=20

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui