From: Alex Riesen <raa.lkml@gmail.com>
To: Thomas Glanzmann <thomas@glanzmann.de>
Cc: git@vger.kernel.org
Subject: Re: merge into branch currently not active / checked out
Date: Sun, 17 Jun 2007 11:45:21 +0200 [thread overview]
Message-ID: <20070617094521.GA2763@steel.home> (raw)
In-Reply-To: <20070617072225.GF23473@cip.informatik.uni-erlangen.de>
Thomas Glanzmann, Sun, Jun 17, 2007 09:22:25 +0200:
> Hello,
> is it possible to merge into a branch currently not active/checked out?
not in current implementation of merge algorithms and conflict
handling.
> I want to merge master in every of the feature branches. Is that possible or
> just bullshit because I don't have a working tree to handle conflicts?
You are _very_ welcome to improve this :) It's not very often need, so
people just do without it (i.e. clone the repo, do a merge there and
pull back).
prev parent reply other threads:[~2007-06-17 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 7:22 merge into branch currently not active / checked out Thomas Glanzmann
2007-06-17 9:27 ` Junio C Hamano
2007-06-17 10:16 ` Thomas Glanzmann
2007-06-20 7:54 ` Karl Hasselström
2007-06-17 9:45 ` Alex Riesen [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=20070617094521.GA2763@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=thomas@glanzmann.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