From: Steven Walter <stevenrwalter@gmail.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git-svn merge helper
Date: Tue, 2 Oct 2007 20:42:52 -0400 [thread overview]
Message-ID: <20071003004252.GA28495@dervierte> (raw)
In-Reply-To: <20071002223813.GA3152@atjola.homenet>
On Wed, Oct 03, 2007 at 12:38:13AM +0200, Björn Steinbrink wrote:
> > The other option is to have a "build" branch. By example:
> >
> > git checkout build
> > git reset --hard master
> > git merge mybranch
> > make
> >
> > In that way, I have branch with the latest changes from head and the
> > changes from mybranch together. The downside to this method is that you
> > may have to repeated resolve merges. Despite the downsides, I find
> > these two methods to work quite well.
>
> Thanks, but it makes no difference here, it stil results in a fast
> forward. This is a small test case which exhibits the behaviour and
> matches my current workflow with git-svn (except for the dcommits):
>
> git init
> echo Hi > file1; git add file1; git commit -m file1
> git checkout -b branch
> echo Hi > file2; git add file2; git commit -m file2
> git checkout master
> echo Hi > file3; git add file3; git commit -m file3
> git checkout branch
> git merge master
>
> # Then I'd normally do the following which causes a fast forward
> #git checkout master
> #git merge branch
>
> # Now I tried this, which also results in a fast-forward:
> git checkout -b merge
> git reset --hard master
> git merge branch
I believe you misunderstood my suggestion. In using a "build" branch,
you would not merge master into branch, as you did above. Instead, you
would create a third, unpublished branch to hold the merge.
At the same time, I have a slightly better understanding of what it is
you're trying to do. If you are trying to keep up an SVN-like workflow
(namely pulling changes from trunk into a branch from time to time),
then my solution probably isn't suitable for you. However, you might
consider why you actually /need/ to do that, outside of SVN convention.
--
-Steven Walter <stevenrwalter@gmail.com>
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
-Robert Heinlein
next prev parent reply other threads:[~2007-10-03 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 11:05 git-svn merge helper Björn Steinbrink
2007-09-30 14:15 ` Benoit SIGOURE
2007-10-01 2:50 ` Björn Steinbrink
2007-10-01 7:56 ` Benoit SIGOURE
[not found] ` <8c5c35580710010113v7d4ad14bt129b7cb12d8f4fb8@mail.gmail.com>
2007-10-02 21:14 ` Björn Steinbrink
2007-10-02 22:04 ` Steven Walter
2007-10-02 22:38 ` Björn Steinbrink
2007-10-03 0:42 ` Steven Walter [this message]
2007-10-03 1:02 ` Björn Steinbrink
2007-10-03 11:40 ` Andreas Ericsson
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=20071003004252.GA28495@dervierte \
--to=stevenrwalter@gmail.com \
--cc=B.Steinbrink@gmx.de \
--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).