From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Junio C Hamano <junkio@cox.net>
Cc: Martin Atukunda <matlads@dsmagic.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add git-explode-packs
Date: Sun, 26 Mar 2006 14:54:50 +0200 [thread overview]
Message-ID: <20060326125450.GT31387@lug-owl.de> (raw)
In-Reply-To: <7vwtehpwdd.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Sat, 2006-03-25 22:12:46 -0800, Junio C Hamano <junkio@cox.net> wrote:
> Martin Atukunda <matlads@dsmagic.com> writes:
> > This script does the opposite of git repack -a -d.
>
> The script seems to do what it claims to, but now why would one
> need to use this? In other words what's the situation one would
> find this useful?
It's possibly useful if you oftenly access old objects with
git-cat-file or git-ls-tree.
Not being a Perl hacker, a friend and I eg. started to hack GIT
support into LXR. I've just posted some very early patches on the LXR
mailing list
(http://sourceforge.net/mailarchive/forum.php?forum_id=1734). What
would be even more interesting is to not unpack _all_ objects, but
only those belonging to specifically mentioned commits or tags. I
think LXR could make _good_ use of that.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-26 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 12:02 [PATCH] Add git-explode-packs Martin Atukunda
2006-03-26 6:12 ` Junio C Hamano
2006-03-26 12:54 ` Jan-Benedict Glaw [this message]
2006-03-27 3:53 ` Junio C Hamano
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=20060326125450.GT31387@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=matlads@dsmagic.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