All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Fix interesting git-rev-list corner case
Date: 30 Jul 2005 22:50:48 +0200	[thread overview]
Message-ID: <m3fytwm313.fsf@telia.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507300913000.29650@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

> On Sat, 30 Jul 2005, Peter Osterlund wrote:
> > 
> > I have problems pulling linux kernel changes from
> > 33ac02aa4cef417871e128ab4a6565e751e5f3b2 to
> > b0825488a642cadcf39709961dde61440cb0731c into my local tree. At first
> > I thought your patch would fix it, but it doesn't:
> 
> No, this is a merge conflict failure, and you simply have conflicts in the
> tree. git did everything right, it just couldn't do an automatic merge.

OK, but note that I didn't do any editing of any local files myself.
Both commit ids are from your public linux kernel git tree. What I did
was equivalent to:

1. rsync from rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
2. waited a day or so.
3. git-pull-script from the same kernel.org repository.

Is it expected that you end up with merge conflicts in this case? If
that's the case, is there a better way to pull changes that doesn't
involve having to resolve conflicts in files you didn't even know
existed?

I think it should be possible to just fast forward to the new HEAD in
this situation.

-- 
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340

  reply	other threads:[~2005-07-30 20:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 22:50 Fix interesting git-rev-list corner case Linus Torvalds
2005-07-30  0:11 ` Ryan Anderson
2005-07-30  1:08   ` A Large Angry SCM
2005-07-30  1:20   ` Linus Torvalds
2005-07-30  1:28     ` Linus Torvalds
2005-07-30 10:10 ` Peter Osterlund
2005-07-30 16:18   ` Linus Torvalds
2005-07-30 20:50     ` Peter Osterlund [this message]
2005-07-30 20:56       ` Linus Torvalds
2005-07-30 21:01         ` Peter Osterlund
2005-07-30 21:32           ` Linus Torvalds
2005-07-30 22:10             ` Linus Torvalds
2005-07-30 23:11               ` Peter Osterlund
2005-07-31  4:44                 ` Linus Torvalds
2005-07-31  5:32                   ` Junio C Hamano

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=m3fytwm313.fsf@telia.com \
    --to=petero2@telia.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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.