How to create branches above master

How to create branches above master

[Bharani Prasad]

Hi,

I am using git-repository along with gerrit server for code review, I want
to create branches called "Integration" branch & "Release" branch 

I got different projects which I need to integrate in "integrate" branch and
give it to testing and once the bugs are fixed it should go to "release"
branch. 

Currently we are using master and private branches...

Please do help me with this issue, as it is critical...

And also can you suggest me what can I use for Continuous build system in
Linux Fedora  

-- 
View this message in context: http://old.nabble.com/How-to-create-branches-above-master-tp29342864p29342864.html
Sent from the git mailing list archive at Nabble.com.

Re: How to create branches above master

[Ævar Arnfjörð Bjarmason]

On Wed, Aug 4, 2010 at 07:22, Bharani Prasad <bharaniprasadvs@gmail.com> wrote:
> I am using git-repository along with gerrit server for code review, I want
> to create branches called "Integration" branch & "Release" branch

What's stopping you? See git-checkout(1) for how to create branches.

> I got different projects which I need to integrate in "integrate" branch and
> give it to testing and once the bugs are fixed it should go to "release"
> branch.

See git-merge(1) et al for how to merge branches.

> Please do help me with this issue, as it is critical...

Please ask more specific questions if you'd like useful answers.

> And also can you suggest me what can I use for Continuous build system in
> Linux Fedora

Buildbot? Any of the intersection between Google's results for
"continuous integration" and "git". They're all good.

Re: How to create branches above master

[Jared Hance]

To Bharani: It sounds like you are using one repository for
multiple projects. Git doesn't handle this use case very well.

On Wed, Aug 04, 2010 at 08:07:56AM +0000, Ævar Arnfjörð Bjarmason wrote:
> > I got different projects which I need to integrate in "integrate" branch and
> > give it to testing and once the bugs are fixed it should go to "release"
> > branch.
> 
> See git-merge(1) et al for how to merge branches.

I think he might need git-cherrypick for this use-case since you don't
want to merge all of integration into release.