From: Krzysztof Halasa <khc@pm.waw.pl>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Something strange has happened to my git HEADs.
Date: Sat, 15 Mar 2008 19:44:29 +0100 [thread overview]
Message-ID: <m3ve3n3jzm.fsf@maximus.localdomain> (raw)
In-Reply-To: <7vwso3n8i5.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sat\, 15 Mar 2008 11\:32\:18 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> lrwx 1 30 2007-10-09 00:55 config -> ~/scm/linux-2.6/config
>> lrwx 1 35 2007-08-24 18:33 description -> ~/scm/linux-2.6/description
>> -rw- 1 126 2008-02-01 21:39 FETCH_HEAD
>> lrwx 1 19 2008-03-15 17:52 HEAD -> refs/heads/eelogger
>> -rw- 1 2220597 2008-03-15 17:56 index
>> drwx 2 4096 2008-03-15 17:57 info
>> -rw- 1 21482 2008-03-15 17:57 info/refs
>> lrwx 1 28 2007-08-24 18:33 logs -> ~/scm/linux-2.6/logs
>> lrwx 1 31 2007-08-24 18:33 objects -> ~/scm/linux-2.6/objects
>> -rw- 1 41 2008-03-15 17:56 ORIG_HEAD
>> -rw- 1 17909 2008-03-15 17:56 packed-refs
>> lrwx 1 28 2007-08-24 18:33 refs -> ~/scm/linux-2.6/refs
>
> This is wrong. How did you set this up initially?
By hand, I'm using that from the beginning (with some incremental
changes). Are only info and packed-refs missing?
> If you are putting a work tree by symlinking contents of its .git
> directory, info and packed-refs are alsy symlinked.
Info seems to have been dropped somehow or maybe never linked in this
directory, but it's not a problem unless I see it again. I just didn't
know about packing references, linking packed-refs made it work.
How about the error message? Seems serious, though git-rebase did its
work.
--
Krzysztof Halasa
prev parent reply other threads:[~2008-03-15 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 17:44 Something strange has happened to my git HEADs Krzysztof Halasa
2008-03-15 17:49 ` Krzysztof Halasa
2008-03-15 18:32 ` Junio C Hamano
2008-03-15 18:44 ` Krzysztof Halasa [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=m3ve3n3jzm.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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