git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [howto] Kernel hacker's guide to git, updated
Date: Fri, 30 Sep 2005 10:36:16 +0200	[thread overview]
Message-ID: <200509301036.16887.oliver@neukum.org> (raw)
In-Reply-To: <7vslvn6m6y.fsf@assigned-by-dhcp.cox.net>

Am Freitag, 30. September 2005 09:37 schrieb Junio C Hamano:
> Oliver Neukum <oliver@neukum.org> writes:
> 
> > Am Donnerstag, 29. September 2005 21:34 schrieb Jon Loeliger:
> >> On Thu, 2005-09-29 at 14:08, Oliver Neukum wrote:
> >> 
> >> > Unfortunately, following the instructions to the letter produces this:
> >> > oliver@oenone:~/linux-2.6> git checkout
> >> > usage: read-tree (<sha> | -m <sha1> [<sha2> <sha3>])
> >> 
> >> Yeah.  See if you still have a .git/HEADS that symlinks
> >> to a valid place or not...?
> >
> > oliver@oenone:~/linux-2.6> ls -la .git/
> > insgesamt 14
> > drwxrwxr-x    6 oliver users  224 2005-09-29 21:06 .
> > drwxr-xr-x    3 oliver users   72 2005-09-29 20:45 ..
> > -rw-rw-r--    1 oliver users   19 2005-05-02 01:02 description
> > lrwxrwxrwx    1 oliver users   17 2005-09-29 21:06 HEAD -> refs/heads/master
> > -rw-------    1 oliver users   32 2005-09-29 21:06 index
> 
> I wonder what that 32-byte small file called 'index' is doing
> there.  If this is the kernel tree, its index file should weigh
> about 1.7MB if I recall correctly.

I have no idea, but the instructions as stated didn't work for me.
Can you replicate that?

	Regards
		Oliver

  reply	other threads:[~2005-09-30  8:37 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 11:03 [howto] Kernel hacker's guide to git, updated Jeff Garzik
2005-09-29 15:18 ` David Leimbach
2005-09-29 16:03   ` Alberto Patino
2005-09-29 16:13     ` David Leimbach
2005-09-29 19:08 ` Oliver Neukum
2005-09-29 19:34   ` Jon Loeliger
2005-09-29 19:38     ` Oliver Neukum
2005-09-30  7:37       ` Junio C Hamano
2005-09-30  8:36         ` Oliver Neukum [this message]
2005-09-30 16:39         ` Linus Torvalds
2005-09-29 20:02 ` Dave Jones
2005-09-29 20:07   ` Anton Altaparmakov
2005-09-29 20:11     ` Dave Jones
2005-09-29 21:14       ` Linus Torvalds
2005-09-29 21:26         ` Linus Torvalds
2005-09-29 21:33           ` Dave Jones
2005-09-29 21:55             ` Linus Torvalds
2005-09-29 22:12               ` Anton Altaparmakov
2005-09-29 22:25                 ` Linus Torvalds
2005-09-29 22:32                   ` Anton Altaparmakov
2005-09-29 23:19                 ` Junio C Hamano
2005-09-30 12:22                   ` Johannes Schindelin
2005-09-29 23:17               ` Horst von Brand
2005-09-30  0:47                 ` Linus Torvalds
2005-09-30  1:54                   ` Junio C Hamano
2005-09-30  2:36                     ` Linus Torvalds
2005-10-01  0:10                   ` Linus Torvalds
2005-10-01  1:58                     ` Horst von Brand
2005-10-03  1:03                       ` Linus Torvalds
2005-09-29 21:33           ` Elfyn McBratney
2005-09-29 21:35           ` Linus Torvalds
2005-09-29 21:40             ` Dave Jones
2005-09-29 20:15   ` Jeff Garzik
2005-09-29 21:04     ` Junio C Hamano
2005-09-30 11:15       ` Jeff Garzik
2005-09-30 11:55         ` Junio C Hamano
2005-09-30 14:11           ` Jeff Garzik
2005-10-02  8:47             ` Junio C Hamano
2005-09-30 18:14           ` Linus Torvalds
2005-10-01  7:36             ` Junio C Hamano
2005-09-30 12:02         ` Oliver Neukum
2005-09-30 13:58           ` Jeff Garzik
2005-09-30 15:10             ` Alberto Patino
2005-09-30 12:07         ` Erik Mouw
2005-09-30 14:08           ` Jeff Garzik
2005-09-30 18:13         ` Horst von Brand
2005-10-01  0:17           ` Jeff Garzik
2005-09-30 22:52         ` Francois Romieu
2005-09-29 21:23     ` Chuck Lever

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=200509301036.16887.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).