git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jan Wielemaker <J.Wielemaker@uva.nl>
Cc: git@vger.kernel.org
Subject: Re: Corruption: empty refs/heads in otherwise filled repo: cannot clone?
Date: Mon, 30 Jun 2008 14:03:57 +0200	[thread overview]
Message-ID: <200806301403.57900.jnareb@gmail.com> (raw)
In-Reply-To: <200806301344.09938.J.Wielemaker@uva.nl>

Jan Wielemaker wrote:

> Summarising, I think the conclusion is that git pack-refs has somehow
> been run on this repository, and being a bare one this is not a
> particulary good idea right now. I have the impression I should `unpack'
> them by putting the appriate files in heads (done) and tags (now still)
> and (re)move packed-refs.

If you use new enough git both on server and on clients it should
not have problems with packed-refs. I would rather check permissions
of $GIT_DIR and $GIT_DIR/packed-refs.

If "git show-ref" and "git for-each-ref" works, then 
"git ls-remote <repo>" should work, and git-fetch/git-clone
shoulw work too...

-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-06-30 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30  9:49 Corruption: empty refs/heads in otherwise filled repo: cannot clone? Jan Wielemaker
2008-06-30 10:10 ` Jakub Narebski
2008-06-30 10:30   ` Jan Wielemaker
2008-06-30 11:26     ` Jakub Narebski
2008-06-30 11:44       ` Jan Wielemaker
2008-06-30 12:03         ` Jakub Narebski [this message]
2008-06-30 12:20           ` Jan Wielemaker
2008-06-30 19:33             ` Daniel Barkalow
2008-06-30 19:46               ` Jan Wielemaker
2008-06-30 11:50       ` Björn Steinbrink

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=200806301403.57900.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=J.Wielemaker@uva.nl \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).