From: Jared Hance <jaredhance@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to create branches above master
Date: Wed, 4 Aug 2010 08:04:22 -0400 [thread overview]
Message-ID: <20100804120421.GA2228@localhost.localdomain> (raw)
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:
> > 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.
prev parent reply other threads:[~2010-08-04 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 7:22 How to create branches above master Bharani Prasad
2010-08-04 8:07 ` Ævar Arnfjörð Bjarmason
2010-08-04 12:04 ` Jared Hance [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100804120421.GA2228@localhost.localdomain \
--to=jaredhance@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).