From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Michael Hendricks <michael@ndrix.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Dissociating a repository from its alternates
Date: Tue, 23 Oct 2007 01:13:31 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710230112131.25221@racer.site> (raw)
In-Reply-To: <20071022233050.GA18430@ginosko.ndrix.org>
Hi,
On Mon, 22 Oct 2007, Michael Hendricks wrote:
> On Mon, Oct 22, 2007 at 08:05:58PM +0100, Johannes Schindelin wrote:
> > On Mon, 22 Oct 2007, Michael Hendricks wrote:
> > > Was such a script ever incorporated into Git?
> >
> > Not that I know of, but "git repack -a && rm
> > .git/objects/info/alternates" should do what you want. You can even
> > make a script of it, add some documentation and a test case, and earn
> > git fame by posting a patch ;-)
>
> With 1.5.3.4, it doesn't appear to work:
>
> $ git clone -s git git2
> Initialized empty Git repository in /Users/michael/src/git2/.git/
>
> $ cd git2
>
> $ git repack -a && rm .git/objects/info/alternates
> Generating pack...
> Done counting 0 objects.
> Nothing new to pack.
>
> $ git status
> # On branch master
> fatal: bad object HEAD
Indeed. Seems that somewhere along the line, repack learnt to imply "-l"
by "-a" or something. Try this instead of "git repack -a":
git rev-parse --all |
git pack-objects --revs .git/objects/pack/pack
(And make sure you read the relevant parts of the documentation to
understand what you're doing ;-)
Hth,
Dscho
next prev parent reply other threads:[~2007-10-23 0:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 7:51 [PATCH] Dissociating a repository from its alternates Junio C Hamano
2007-02-15 9:37 ` [PATCH +1] " Junio C Hamano
2007-02-15 15:39 ` [PATCH] " Johannes Schindelin
2007-02-16 20:13 ` Junio C Hamano
2007-10-22 18:04 ` Michael Hendricks
2007-10-22 19:05 ` Johannes Schindelin
2007-10-22 23:30 ` Michael Hendricks
2007-10-23 0:13 ` Johannes Schindelin [this message]
2007-02-16 19:11 ` James Cloos
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=Pine.LNX.4.64.0710230112131.25221@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=michael@ndrix.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).