git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to create branches above master

From
Jared Hance <jaredhance@gmail.com>
Date
Aug 4, 2010, 12:04 UTC
Message-ID
<20100804120421.GA2228@localhost.localdomain>
In-Reply-To
<AANLkTik-qw3bFHWLwMnqJuzgu=HHSRiiVRBW2nfjRTy3@mail.gmail.com>

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:
Show 5 quoted lines
> > 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.

Previous: Ævar Arnfjörð Bjarmason
Message 3 of 3 in “How to create branches above master”
  1. Bharani PrasadAug 4, 2010
  2. Ævar Arnfjörð BjarmasonAug 4, 2010
  3. Jared HanceAug 4, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.