From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Brandon Casey" <casey@nrlssc.navy.mil>
Cc: "Lars Hjemli" <hjemli@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
hanwen@xs4all.nl, git@vger.kernel.org
Subject: Re: Spam: Re: git branch performance problem?
Date: Thu, 11 Oct 2007 10:41:06 +0100 [thread overview]
Message-ID: <e2b179460710110241i445bc61ep8ae60e421c19c0f0@mail.gmail.com> (raw)
In-Reply-To: <470D585D.1030808@nrlssc.navy.mil>
On 10/10/07, Brandon Casey <casey@nrlssc.navy.mil> wrote:
> No, this is not the case, unless something has changed very recently
> in git-gc or git-repack. Even git-gc with no arguments is unsafe if
> the repository being gc'ed is listed in another's alternates.
>
> git-gc calls repack with -a and -d. which causes a new pack to be
> created which only contains the objects required by the local repository.
> The other packs are then deleted. Objects contained in those packs and
> required by a "sharing" repository (one using the alternates mechanism)
> will be deleted if the local repository no longer references them.
It's not something I've really looked into, but there seems to be a
reflogs mechanism which can temporarily pin an otherwise unreferenced
object so it doesn't get deleted. Would it be possible to populate the
remote's view of referenced objects into this, at the point of clone,
push or pull, which would seem to be the points at which this might be
changing.
Obviously this is of no use if you're 'anonymously' poncing off a
third repo to save clone time, but if you're in control of both repo's
it might be useful.
Mike
next prev parent reply other threads:[~2007-10-11 9:42 UTC|newest]
Thread overview: 25+ 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
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 [this message]
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
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=e2b179460710110241i445bc61ep8ae60e421c19c0f0@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=bfields@fieldses.org \
--cc=casey@nrlssc.navy.mil \
--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).