From: Michael J Gruber <git@drmicha.warpmail.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Thomas Schwinge <thomas@schwinge.name>, git@vger.kernel.org
Subject: Re: Removing alternates -- but how?
Date: Wed, 14 Apr 2010 09:25:43 +0200 [thread overview]
Message-ID: <4BC56DF7.4030502@drmicha.warpmail.net> (raw)
In-Reply-To: <20100413155819.GI19595@genesis.frugalware.org>
Miklos Vajna venit, vidit, dixit 13.04.2010 17:58:
> On Tue, Apr 13, 2010 at 02:57:04PM +0200, Thomas Schwinge <thomas@schwinge.name> wrote:
>> $ cat .git/objects/info/alternates
>> ../../../glibc/.git/objects
>> ../../../../O/work.new/.git/objects
>> $ git repack -a
>> Counting objects: 18670, done.
>> Compressing objects: 100% (7655/7655), done.
>> Writing objects: 100% (18670/18670), done.
>> Total 18670 (delta 10218), reused 18670 (delta 10218)
>> $ mv .git/objects/info/alternates{,.DEFUNCT}
>> $ git branch
>> error: refs/remotes/grubber/master does not point to a valid object!
>> error: refs/remotes/sourceware/cvs/fedora-2_3-branch does not point to a valid object!
>> error: refs/remotes/sourceware/cvs/fedora-2_5-branch does not point to a valid object!
>> [...]
>> error: refs/tags/cvs/sparc-980522-merge does not point to a valid object!
>> error: refs/tags/cvs/start does not point to a valid object!
>> error: refs/tags/master-2008-11-27 does not point to a valid object!
>> error: refs/tags/master-2009-02-10 does not point to a valid object!
>> error: refs/tags/master-2009-07-10 does not point to a valid object!
>> error: refs/top-bases/t/IOCTL_decode_argument does not point to a valid object!
>> error: refs/top-bases/t/IOCTL_types does not point to a valid object!
>> error: refs/top-bases/t/____longjmp_chk_cleanup_linux_x86_64 does not point to a valid object!
>> error: refs/top-bases/t/bits_posix_opt.h__POSIX_THREADS does not point to a valid object!
>> error: refs/top-bases/t/bits_pthreadtypes.h does not point to a valid object!
>> baseline
>> posix/regex_internal.c/MAX_undefined
>> t/IOCTL_decode_argument
>> t/IOCTL_types
>> t/____longjmp_chk
>> t/____longjmp_chk_cleanup_linux_x86_64
>> t/__rtld_lock_recursive_t
>> [...]
>> t/verify.h
>> * tschwinge/Roger_Whittaker
>
> What git version are you using?
>
> It seems to work for me:
>
> $ mkdir s
> $ cd s
> $ git init
> $ echo a > a
> $ git add a
> $ git commit -m i
> $ cd ..
> $ git clone -s s c
> $ cd c
> $ git repack -a
> $ mv .git/objects/info/alternates .git/objects/info/alternates.orig
> $ git branch
> * master
Well, according to the log it worked for some branches for Thomas, just
not for all of them. I'm not surprised your test succeeds. In Thomas'
case it seems that repack is missing some dependencies, but it doesn't
even have an --all option or such.
Thomas: In addition to your git version, it would be good to know
whether you use any of
- grafts
- replaced objects
- multiple roots (branches without common commits)
- alternate chains (source repo borrowing objects from a third repo)
Michael
prev parent reply other threads:[~2010-04-14 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 12:57 Removing alternates -- but how? Thomas Schwinge
2010-04-13 15:58 ` Miklos Vajna
2010-04-14 7:25 ` Michael J Gruber [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=4BC56DF7.4030502@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=thomas@schwinge.name \
--cc=vmiklos@frugalware.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).