From: Alex Riesen <raa.lkml@gmail.com>
To: Carlo Wood <carlo@alinoe.com>,
Daniel Barkalow <barkalow@iabervon.org>,
linux-kernel@vger.kernel.org
Subject: Re: My kernel hangs again: Help with git please
Date: Sun, 17 Jun 2007 12:52:27 +0200 [thread overview]
Message-ID: <20070617105226.GA22912@steel.home> (raw)
In-Reply-To: <20070616140340.GA30861@alinoe.com>
Carlo Wood, Sat, Jun 16, 2007 16:03:40 +0200:
> $ git merge origin
> fatal: Needed a single revision
> Usage: /usr/bin/git-merge [-n] [--no-commit] [--squash] [-s <strategy>]... <merge-message> <head> <remote>+
>
> For some reason I don't think I should be needing commands that need
> "<merge-message>"; I don't want to change the (local) tree in anyway.
I'd recommend to upgrade your git. There are some really nice
improvements in the latest versions (1.5.2.2, for instance).
Particularly, the command above would have worked. That is, assuming
you actually do have that origin branch. In any case, a
$ git fetch git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git master
$ git reset --hard FETCH_HEAD
will get you the very latest kernel in your working directory. Has
some disadvantages, though: does not retrieve the tags and destroys
local changes.
But you'll find a man page of git-remote and git-config very
interesting, especially wrt the above operation. I do just "git pull",
for example and actually _am_ sure I get the latest kernel, get all
the tags and never loose local changes.
prev parent reply other threads:[~2007-06-17 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 0:12 Carlo Wood
2007-06-16 0:33 ` Daniel Barkalow
2007-06-16 4:07 ` Carlo Wood
2007-06-16 5:28 ` Daniel Barkalow
2007-06-16 14:03 ` Carlo Wood
2007-06-16 19:13 ` Daniel Barkalow
2007-06-17 10:52 ` Alex Riesen [this message]
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=20070617105226.GA22912@steel.home \
--to=raa.lkml@gmail.com \
--cc=barkalow@iabervon.org \
--cc=carlo@alinoe.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®