git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: git@vger.kernel.org
Subject: linux-x86-tip: pilot error?
Date: Sun, 22 Jun 2008 05:36:20 -0700	[thread overview]
Message-ID: <20080622123620.GA9328@linux.vnet.ibm.com> (raw)

Hello, Ingo,

I took the precaution of rebuilding my linux-2.6-tip from scratch as follows:

  544  mkdir linux-2.6-tip
  545  cd linux-2.6-tip
  546  git-init-db
  547  git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
  548  git-remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
  549  git-remote update
  550  git-checkout tip-core-rcu-2008-06-16_09.23_Mon

The "git-checkout" command complained as follows:

	warning: You appear to be on a branch yet to be born.
	warning: Forcing checkout of tip-core-rcu-2008-06-16_09.23_Mon.
	Checking 24254 files out...
	 100% (24254/24254) done
	fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
	Use '--' to separate paths from revisions
	Cannot detach HEAD

In addition, the kernel/rcutorture.c file does not have the "stutter"
changes in it after doing this checkout.

Did I mess something up?  Am I working with a too-old version of git
(git version 1.5.2.5)?  Or has git simply taken a deep and personal
disliking to me?  ;-)

My next step will be to try a more recent version of git.  In parallel,
I will just re-do the patch on top of my patch stack.

							Thanx, Paul

PS.  I am assuming that the repeated messages from git-update of
     the following form are expected behavior when there are tags:

     * refs/tags/tip-x86-xsave-2008-05-26_08_54_Mon: storing tag 'tip-x86-xsave-2008-05-26_08_54_Mon' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
       commit: d40ace0

             reply	other threads:[~2008-06-22 12:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 12:36 Paul E. McKenney [this message]
2008-06-22 12:48 ` linux-x86-tip: pilot error? Mikael Magnusson
2008-06-22 13:21   ` Paul E. McKenney
2008-06-22 21:11     ` Mikael Magnusson
2008-06-22 21:42     ` Björn Steinbrink
2008-06-22 22:21       ` Paul E. McKenney
2008-06-23  7:14     ` Ingo Molnar
2008-06-23  9:57       ` Paul E. McKenney
2008-06-23 10:24         ` Ingo Molnar
2008-06-23 11:11           ` Paul E. McKenney
2008-06-23 11:22             ` Ingo Molnar
2008-06-23 16:14               ` Daniel Barkalow
2008-06-23 15:12       ` Jeff King
2008-06-23 15:31         ` Ingo Molnar
2008-06-23 16:05         ` Ingo Molnar

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=20080622123620.GA9328@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=git@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).