From: Michael Geddes <michael@frog.wheelycreek.net>
To: git@vger.kernel.org
Subject: Bug in alternates
Date: Thu, 12 Aug 2010 08:26:52 +0800 [thread overview]
Message-ID: <201008120826.53902.michael@frog.wheelycreek.net> (raw)
Hi - I had a bit of a hiccup with git yesterday - there's a bit of a story to
it, which at the least might be amusing. There's script to reproduce at the
bottom if you don't care for the story.
I had done a
git clone --reference Foo git@host:Foo Foo.New
then after getting it right, I did
mv Foo Foo.old
mv Foo.New Foo
Then I had all these missing references, and I thought .. oh yeah, that's
cause it can't find the references.. well I don't really know how to change
that (I do now), but I want all the objects in that directory anyway for when
I delete the Foo.old directory..
so I did a
cd Foo
git fetch
.. so all was good for a while.. It was all there and hunky-dory.
Then.. the fated git gui 'garbage collect' dialogue appeared, and I thought,
"why not", so I did.
At that point, git decided to pack all the references (yay) .. and then it
said.. hmm.. are those available in my alternates .. let's see
..Foo/.git/objects .. yeah - all those objects are there.. so I can just
remove that pack.
Woops.
If you're not following the story, the Foo repo had itself as an alternate.
Include me in replies please- I'm not on the list.
//.ichael Geddes
Here's the script:
------------8<-----------testalt--------------
#!/bin/sh
mkdir testaltrep
cd testaltrep
git init
for i in 1 2 3 4 5 6 7 8 9 ; do
touch $i.txt
git add $i.txt
done
git commit -m "Commit"
echo "$PWD/.git/objects" > .git/objects/info/alternates
# Seems like it has to be done like this to get it to repack.
git repack -adl && git repack -ad && git repack -adl
if git checkout master ; then
echo OK
ret=0
else
echo BAD Unable to checkout reference
ret=1
fi
cd ..
rm -rf testaltrep
exit ${ret}
next reply other threads:[~2010-08-12 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 0:26 Michael Geddes [this message]
2010-08-12 0:50 ` Bug in alternates Chris Packham
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=201008120826.53902.michael@frog.wheelycreek.net \
--to=michael@frog.wheelycreek.net \
--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).