From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: torvalds@linux-foundation.org, git@vger.kernel.org
Subject: Re: linux-2.6.git/packed-refs???
Date: Tue, 13 Feb 2007 13:16:10 -0500 [thread overview]
Message-ID: <20070213181610.GA2782@thunk.org> (raw)
In-Reply-To: <7v7ium1k7s.fsf@assigned-by-dhcp.cox.net>
On Tue, Feb 13, 2007 at 01:27:03AM -0800, Junio C Hamano wrote:
> I noticed while scanning #git log that it appears that pack-refs
> was run in your public repo and some people cannot clone over
> dumb protocols with older git.
>
> commit 2986c02217f98809d8990e7679edf0f5d99f904d
> Author: Junio C Hamano <junkio@cox.net>
> Date: Wed Nov 22 22:24:09 2006 -0800
>
> git-fetch: fix dumb protocol transport to fetch from pack-pruned ref
>
> was the first revision that aligned dumb protocol clients with
> pack-ref; unfortunately anything older will not find the ref
> that was packed.
Stupid question. Suppose someone has run git pack-refs on a
repository. What is the recommended way to reverse the process. Is
the answer is to clone the repository and then throw away the original
one? Is there another way to do it?
- Ted
next prev parent reply other threads:[~2007-02-13 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 9:27 linux-2.6.git/packed-refs??? Junio C Hamano
2007-02-13 9:48 ` [PATCH] Do not run git-pack-refs by default for now from git-gc Junio C Hamano
2007-02-13 10:03 ` Johannes Schindelin
2007-02-13 10:29 ` Jeff King
2007-02-13 10:55 ` Johannes Schindelin
2007-02-13 17:59 ` Junio C Hamano
2007-02-13 13:01 ` [PATCH] git-gc: run pack-refs by default unless the repo is bare Johannes Schindelin
2007-02-13 18:16 ` Theodore Tso [this message]
2007-02-13 18:41 ` linux-2.6.git/packed-refs??? Johannes Schindelin
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=20070213181610.GA2782@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.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).