From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932297Ab2K1Ufz (ORCPT ); Wed, 28 Nov 2012 15:35:55 -0500 Received: from mail-we0-f174.google.com ([74.125.82.174]:42523 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932085Ab2K1Ufy (ORCPT ); Wed, 28 Nov 2012 15:35:54 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Wed, 28 Nov 2012 12:35:32 -0800 X-Google-Sender-Auth: l4KoLPSEn-YttZY8r2nejaC0rP8 Message-ID: Subject: Re: [git pull] drm fixes To: Dave Airlie Cc: Dave Airlie , Linux Kernel Mailing List , DRI mailing list Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ Hmm. For some reason this seems to have never gone out, and was in my drafts folder. If you get it twice, my bad ] On Thu, Nov 22, 2012 at 12:57 AM, Dave Airlie wrote: > > Doh!, yes I picked wrong place to generate report from, okay here is > one corresponding to what you saw, You should never even need to "pick" any place to generate the report from. Just do something like git fetch upstream (where "upstream" is a branch description for the upstream repository - see "man git-remote" etc, although you can obviously always just type out the whole repo details etc in full if you would want to). Note the "fetch" - not pull - you just want to get it, not merge it. Then you can just point git pull-request at the upstream, and git wll figure out what the latest common point is. No need for you to manually try to figure it out. Linus