From: Linus Torvalds <torvalds@osdl.org>
To: Chuck Lever <cel@citi.umich.edu>
Cc: Carl Baldwin <cnb@fc.hp.com>, "H. Peter Anvin" <hpa@zytor.com>,
Git Mailing List <git@vger.kernel.org>,
Catalin Marinas <catalin.marinas@gmail.com>
Subject: Re: auto-packing on kernel.org? please?
Date: Mon, 21 Nov 2005 21:41:17 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0511212134330.13959@g5.osdl.org> (raw)
In-Reply-To: <4382AC11.5090209@citi.umich.edu>
On Tue, 22 Nov 2005, Chuck Lever wrote:
>
> there are some things repacking does that breaks StGIT, though.
>
> git repack -d
>
> seems to remove old commits that StGIT was still depending on.
If that is true, then "git-fsck-cache" probably also reports errors on a
StGIT repository. No? Basically, it implies that the tool doesn't know how
to find all the "heads".
Could somebody (Catalin?) perhaps tell how tools like git-fsck-cache and
git-repack could figure out which objects are still in use by stgit?
Preferably with some generic mechanism that _other_ projects (not just
stgit) might want to use?
The preferred way would be to just list the references somewhere under
.git/refs/stgit, in which case fsck and repack should pick them up
automatically (so clearly stgit doesn't do that right now ;).
It also implies that doing a "git prune" will do horribly bad things to a
stgit repo, since it would remove all the objects that it thinks aren't
reachable..
> git repack -a -n
>
> seems to work fine with StGIT,
Well, it "works", but not "fine". Since it doesn't know about the stgit
objects, it won't ever pack them.
But maybe that's what stgit wants (since they are "temporary"), but it
does mean that if you see a big advantage from packing, you might be
losing some of it.
Linus
next prev parent reply other threads:[~2005-11-22 5:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 18:44 auto-packing on kernel.org? please? Linus Torvalds
[not found] ` <434EABFD.5070604@zytor.com>
[not found] ` <434EC07C.30505@pobox.com>
2005-10-13 21:23 ` [kernel.org users] " Linus Torvalds
2005-10-16 14:33 ` Dirk Behme
2005-10-16 15:44 ` Daniel Barkalow
2005-10-16 16:12 ` Nick Hengeveld
2005-10-16 16:23 ` Brian Gerst
2005-10-16 16:56 ` Junio C Hamano
2005-10-16 21:33 ` Nick Hengeveld
2005-10-16 22:12 ` Junio C Hamano
2005-10-17 6:06 ` Nick Hengeveld
2005-10-17 8:21 ` Junio C Hamano
2005-10-17 17:41 ` Nick Hengeveld
2005-10-17 20:08 ` Junio C Hamano
2005-10-17 22:56 ` Daniel Barkalow
2005-10-17 23:19 ` Linus Torvalds
2005-10-17 23:54 ` Nick Hengeveld
2005-10-17 19:13 ` Daniel Barkalow
2005-10-16 17:10 ` Johannes Schindelin
2005-10-16 17:15 ` Brian Gerst
2005-11-21 19:01 ` Carl Baldwin
2005-11-21 19:24 ` Linus Torvalds
2005-11-21 19:58 ` Junio C Hamano
2005-11-21 20:38 ` Linus Torvalds
2005-11-21 21:35 ` Junio C Hamano
2005-11-22 5:26 ` Chuck Lever
2005-11-22 5:41 ` Linus Torvalds [this message]
2005-11-22 14:13 ` Catalin Marinas
2005-11-22 17:05 ` Linus Torvalds
[not found] ` <7v64qkfwhe.fsf@assigned-by-dhcp.cox.net>
[not found] ` <b0943d9e0511220946o3b62842ey@mail.gmail.com>
[not found] ` <7v1x18eddp.fsf@assigned-by-dhcp.cox.net>
2005-11-23 14:10 ` Catalin Marinas
2005-11-22 18:18 ` Chuck Lever
2005-11-23 14:18 ` Catalin Marinas
2005-11-22 17:25 ` Carl Baldwin
2005-11-22 17:58 ` Linus Torvalds
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=Pine.LNX.4.64.0511212134330.13959@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=catalin.marinas@gmail.com \
--cc=cel@citi.umich.edu \
--cc=cnb@fc.hp.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.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).