From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Andrew Arnott" <andrewarnott@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to merge branches except for one commit
Date: Wed, 28 May 2008 22:42:16 -0400 [thread overview]
Message-ID: <32541b130805281942g2550cad9k7ba530c59e050aa4@mail.gmail.com> (raw)
In-Reply-To: <216e54900805281932v1397fd30sad91f767175ba95e@mail.gmail.com>
On 5/28/08, Andrew Arnott <andrewarnott@gmail.com> wrote:
> At some point, most or all the commits on master since branching off
> v1.0 I want to include in the v1.1 release.
I think this is perhaps the root of your problem. Normally people
don't merge from master into their bugfix release; they do it the
other way around, making bugfixes in the bugfix branch, and merging
them occasionally into master.
Or alternatively, they cherry pick just *some* of the changes from
master back into the bugfix release, because presumably there are also
a bunch of non-critical new feature patches sitting in master.
If you really want to do it the way you described, an easy answer
might be to just merge the entire master into v1.1, then "git revert"
(in v1.1) the patch that changes the version number :)
Have fun,
Avery
next prev parent reply other threads:[~2008-05-29 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 2:32 How to merge branches except for one commit Andrew Arnott
2008-05-29 2:42 ` Avery Pennarun [this message]
2008-05-29 3:01 ` Andrew Arnott
2008-05-29 15:13 ` Andreas Ericsson
2008-05-29 4:24 ` Junio C Hamano
2008-05-29 4:38 ` Imran M Yousuf
2008-05-29 5:42 ` Andrew Arnott
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=32541b130805281942g2550cad9k7ba530c59e050aa4@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=andrewarnott@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).