From: "Han-Wen Nienhuys" <hanwenn@gmail.com>
To: "Lars Hjemli" <hjemli@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git branch performance problem?
Date: Wed, 10 Oct 2007 18:30:02 -0300 [thread overview]
Message-ID: <f329bf540710101430i63926b25q7d55976af96b891d@mail.gmail.com> (raw)
In-Reply-To: <f329bf540710101424q22309489sada99907e94b2cd0@mail.gmail.com>
2007/10/10, Han-Wen Nienhuys <hanwenn@gmail.com>:
> More to the point, I seemed to have lost my entire repository. This is
> the type of surprise I don't enjoy.
>
> Now, can someone explain why 'git branch' takes forever if there are
> only two non-remote branches ?
So,
Here is a question: I would like to share commitishes between two checkouts
of a repository. The reason for this is that I want to easily cherry
pick back and forth between the two. The files of in one of them
should be continually available, since I am running out of that
directory.
The way I solved that, was to have both repositories pointing to each
other, using alternates.
Now, after a couple of gc and pack-refs iterations, I am greeted by
hanwen@lilypond:~/vc/git6$ git fsck
missing tree 12b00ec3190f7b46a5fe0a3235445bead4c9645b
broken link from tree 1718d09e0394d113c162e4a3471e7a1f20914a94
to blob 635e2802568b85017007698c0e6dd4d28dca496f
broken link from tree 926899798fce75038e24f8fa1838f6da8bcf105f
to tree f1b852d270ebbaaf95d8ddc06c52763bad11ff25
missing blob 99f0c0d63276fce444e3a200167b636236784c52
missing tree f1b852d270ebbaaf95d8ddc06c52763bad11ff25
missing blob 236962a87fafae8ca2dce2dc550d344aa7a8884a
missing blob 7d69ca297f392a954c4cdcb62bb4c8a90ddb862b
missing blob 9e39be8f5cb4eeff97fcfd6eb77fefeda02f0e71
dangling blob f3a93f023080ce9fc6becb397e366cc4ceb192f5
could it be that GC does not handle cyclic alternates correctly?
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2007-10-10 21:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 20:22 git branch performance problem? Han-Wen Nienhuys
2007-10-10 20:44 ` Lars Hjemli
2007-10-10 21:17 ` Han-Wen Nienhuys
2007-10-10 21:24 ` Han-Wen Nienhuys
2007-10-10 21:30 ` Han-Wen Nienhuys [this message]
2007-10-10 21:39 ` J. Bruce Fields
2007-10-10 21:45 ` Lars Hjemli
2007-10-10 21:49 ` Han-Wen Nienhuys
2007-10-10 21:53 ` J. Bruce Fields
2007-10-10 22:01 ` Han-Wen Nienhuys
2007-10-10 21:53 ` Johannes Schindelin
2007-10-10 22:55 ` Spam: " Brandon Casey
2007-10-11 9:41 ` Mike Ralphson
2007-10-11 10:58 ` Johannes Schindelin
2007-10-10 23:39 ` Linus Torvalds
2007-10-11 2:26 ` Han-Wen Nienhuys
2007-10-11 6:41 ` Alex Riesen
2007-10-11 10:46 ` Johannes Schindelin
2007-10-11 13:11 ` Han-Wen Nienhuys
2007-10-11 15:16 ` Linus Torvalds
2007-10-12 17:19 ` Salikh Zakirov
2007-10-10 21:34 ` Lars Hjemli
2007-10-10 21:54 ` [PATCH] git-branch: only traverse the requested refs Lars Hjemli
2007-10-10 23:00 ` Johannes Schindelin
2007-10-10 23:30 ` Lars Hjemli
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 17:32 git branch performance problem? Salikh Zakirov
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=f329bf540710101430i63926b25q7d55976af96b891d@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--cc=hjemli@gmail.com \
/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).