From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: joe@perches.com
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: net-2.6.25 being rebased...
Date: Tue, 11 Dec 2007 13:31:29 -0800 [thread overview]
Message-ID: <475F01B1.2080400@intel.com> (raw)
In-Reply-To: <20071211.130858.134618588.davem@davemloft.net>
David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Tue, 11 Dec 2007 13:04:59 -0800
>
>> On Tue, 2007-12-11 at 11:56 -0800, David Miller wrote:
>>> The rebase of net-2.6.25 is complete
>> I have an earlier unmodified git repository of net-2.6.25.
>> Does anyone know the appropriate git commands to resync
>> to the rebased content?
>>
>> $ git branch
>> * master
>> $ git-pull
>> [...]
>> Automatic merge failed; fix conflicts and then commit the result.
>
> Easiest thing to do is do a quick local clone of Linus's current tree
> (you do have one of these around right? :-) and then pull in from the
> rebased tree.
>
> bash$ git clone linux-2.6/.git net-2.6.25
> bash$ git pull git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.25.git
I often have success without recloning by doing:
$ git-reset --hard v2.6.23
$ git pull git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.25.git
saves you the time to reclone. As long as you reset below the rebase point, this
should be OK.
Auke
next prev parent reply other threads:[~2007-12-11 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 17:26 net-2.6.25 being rebased David Miller
2007-12-11 19:56 ` David Miller
2007-12-11 21:04 ` Joe Perches
2007-12-11 21:08 ` David Miller
2007-12-11 21:31 ` Kok, Auke [this message]
2007-12-11 21:09 ` Arnaldo Carvalho de Melo
2007-12-11 21:23 ` Joe Perches
2007-12-11 21:35 ` Francois Romieu
2007-12-11 21:49 ` Francois Romieu
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=475F01B1.2080400@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@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.