From: Pavel Roskin <proski@gnu.org>
To: bruno randolf <bruno@thinktube.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: merge errors on 'everything'
Date: Tue, 08 Jan 2008 21:13:55 -0500 [thread overview]
Message-ID: <1199844835.3697.12.camel@dv> (raw)
In-Reply-To: <200801091043.02204.bruno@thinktube.com>
On Wed, 2008-01-09 at 10:43 +0900, bruno randolf wrote:
> hi!
>
> many times when i do a 'git pull' to update the wireless-2.6 'everything'
> branch i run into unexplicable merge errors.
I think the explanation is that the changes in the branch are rebased,
rather than merged, when the wireless-2.6 repository is updated from the
upstream Linux repository.
git views changes on top of the old tree in your repository as
independent from those that appear in wireless-2.6, so it tries to merge
them. But since it's actually the same patches, git sees that as a
conflict.
You can clean up the consequences of the failed merge by running
"git-reset --hard origin/everything" where "origin" is the name of the
remote.
> i created the branch with 'git co --track -b everything origin/everything' and
> i don't work on this branch so all files are un-modified.
>
> what am i doing wrong?
I'm not sure you are doing anything wrong. It's quite possible that git
should be changed to handle this problem better. Or maybe the
wireless-2.6 repository should be managed differently.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-01-09 2:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 1:43 merge errors on 'everything' bruno randolf
2008-01-09 1:51 ` John W. Linville
2008-01-09 2:32 ` Pavel Roskin
2008-01-09 9:05 ` Kalle Valo
2008-01-10 1:29 ` bruno randolf
2008-01-10 9:43 ` Andreas Schwab
2008-01-10 10:00 ` Kalle Valo
2008-01-10 15:34 ` John W. Linville
2008-01-19 9:28 ` bruno randolf
2008-01-13 13:10 ` David Woodhouse
2008-01-15 10:11 ` Kalle Valo
2008-01-09 2:13 ` Pavel Roskin [this message]
2008-01-09 9:44 ` Andreas Schwab
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=1199844835.3697.12.camel@dv \
--to=proski@gnu.org \
--cc=bruno@thinktube.com \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.