From: Kevin Daudt <me@ikke.info>
To: Anatoly Borodin <anatoly.borodin@gmail.com>
Cc: webmaster@peter-speer.de, git <git@vger.kernel.org>
Subject: Re: git branches & merge
Date: Thu, 13 Oct 2016 17:49:59 +0200 [thread overview]
Message-ID: <20161013154959.GB1698@ikke.info> (raw)
In-Reply-To: <CACNzp2nG1KfFuiSH1UUGVSz1T39PjzfDgCp6vqOVe7-Lph2yNw@mail.gmail.com>
On Wed, Oct 12, 2016 at 04:43:07PM +0200, Anatoly Borodin wrote:
> Hi,
>
>
> the IP will not be overwritten, you'll still have the new IP in
> master. Nothing to worry about :)
>
>
To expand on that, git does a so called 3-way merge. This means git will
look for a common base commit, and compare changes from both sides to
see which side actually made a change.
In your case, the base and the release branch both should show the old
ip, and the master side would show the new IP. This tells git that
master has changed, and not the release branch, and takes the master
side of the change, resulting the new IP to show up.
Hope this helps, Kevin.
prev parent reply other threads:[~2016-10-13 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 13:50 git branches & merge webmaster
2016-10-12 14:43 ` Anatoly Borodin
2016-10-13 15:49 ` Kevin Daudt [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=20161013154959.GB1698@ikke.info \
--to=me@ikke.info \
--cc=anatoly.borodin@gmail.com \
--cc=git@vger.kernel.org \
--cc=webmaster@peter-speer.de \
/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).