From: Chris Packham <judge.packham@gmail.com>
To: Michael Geddes <michael@frog.wheelycreek.net>
Cc: git@vger.kernel.org
Subject: Re: Bug in alternates
Date: Wed, 11 Aug 2010 17:50:11 -0700 [thread overview]
Message-ID: <4C634543.5020301@gmail.com> (raw)
In-Reply-To: <201008120826.53902.michael@frog.wheelycreek.net>
On 11/08/10 17:26, Michael Geddes wrote:
> If you're not following the story, the Foo repo had itself as an alternate.
>
I had done a little messing with putting a UI around alternates a while
back (if I ever find those elusive round tuits I'll pick it up again).
There are also more complicated cases where you could end-up recursively
including yourself, I managed to do that at least once in my messing
around.
It shouldn't be too hard to add some safety checks to git gc or git
repack but they should take the possibility of recursive alternates into
account.
> Include me in replies please- I'm not on the list.
>
That's the norm around here.
prev parent reply other threads:[~2010-08-12 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 0:26 Bug in alternates Michael Geddes
2010-08-12 0:50 ` Chris Packham [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=4C634543.5020301@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=michael@frog.wheelycreek.net \
/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).