From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: git-merge: need a tap with the cluestick, please
Date: Thu, 18 Oct 2007 09:17:55 -0700 [thread overview]
Message-ID: <ff80tr$hh1$1@ger.gmane.org> (raw)
I just tried my first local modification to Linus's tree, and I
can't get the merge to work. Maybe my whole approach is wrong?
I wanted start compiling the kernel out-of-tree, so I added my
own 'obj' directory at the top level.
I then got conflicts when trying to pull from Linus, so I added
my 'obj' directory to my toplevel .gitignore file and committed
the local change to my 'master' branch. (This is my only local
modification because I'm only tracking Linus, not developing the
kernel.)
Now when I pull from Linus the merge stops in the middle because of
conflicts with my .gitignore file <sigh>. Anything I try now with
git-merge tells me I can't do that in the middle of a conflicted
merge. Yes, I know that now, but what should I do instead?
I could move my 'obj' out-of-tree but then I wouldn't learn anything.
This has to be bone-head easy, but not for me :)
Clues most welcome.
next reply other threads:[~2007-10-18 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 16:17 walt [this message]
2007-10-18 23:35 ` git-merge: need a tap with the cluestick, please Shawn O. Pearce
2007-10-19 1:00 ` walt
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='ff80tr$hh1$1@ger.gmane.org' \
--to=wa1ter@myrealbox.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).