From: Lane Brooks <lane@brooks.nu>
To: Git List <git@vger.kernel.org>
Subject: How to manage merges from one line while excluding its merges from another
Date: Fri, 25 Jun 2010 16:26:36 -0600 [thread overview]
Message-ID: <4C252D1C.4010702@brooks.nu> (raw)
I have a tree like this:
G---H---I---J---K devel
/ / /
A---B---C---D---E---F main
\
L---M---N---O my
The 'my' branch forked off the 'main' line and for reasons out of my
control cannot merge the 'main' changes (D,E,F) back.
The 'devel' line is a another line that I need to track and merge from,
but I only want the changes local to that branch that are not on from
the mainline. i.e., I only want commits G,H,J.
I want to continue to merge from the devel line as additional commits
are made that are not on the main branch, but I do not want any of the
future merge commits.
Is there an automated way to do this or do I have to cherry pick
everything by hand?
Thanks,
Lane
next reply other threads:[~2010-06-25 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 22:26 Lane Brooks [this message]
2010-06-26 0:03 ` How to manage merges from one line while excluding its merges from another Jonathan Nieder
2010-06-26 0:35 ` Lane Brooks
2010-06-26 0:51 ` Jonathan Nieder
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=4C252D1C.4010702@brooks.nu \
--to=lane@brooks.nu \
--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).