From: Nicolas Pitre <nico@fluxnic.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Shawn O. Pearce" <spearce@spearce.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Remove diff machinery dependency from read-cache
Date: Thu, 21 Jan 2010 21:35:08 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001212131230.1726@xanadu.home> (raw)
In-Reply-To: <7v636vj7c2.fsf@alter.siamese.dyndns.org>
On Thu, 21 Jan 2010, Junio C Hamano wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> > On Thu, 21 Jan 2010, Linus Torvalds wrote:
> >>
> >> We could fix it a few ways
> >>
> >> - ignore it. Most git programs will get the pack handling functions
> >> anyway, since they want to get object reading.
> >
> > In fact, we should probably remove git-show-index. It may have some
> > historical significance as a pack-file index debugger, but it has no
> > actual redeeming features now, considering that the binary is a megabyte
> > of useless crud with debugging info.
> >
> > However, we do actually use it in t/t5302-pack-index.sh. So in the
> > meantime, how about this hacky patch to simply just avoid xmalloc, and
> > separating out the trivial hex functions into "hex.o".
> >
> > This results in
> >
> > [torvalds@nehalem git]$ size git-show-index
> > text data bss dec hex filename
> > 222818 2276 112688 337782 52776 git-show-index (before)
> > 5696 624 1264 7584 1da0 git-show-index (after)
> >
> > which is a whole lot better, no?
> >
> > (Or make it a built-in, if we actually think we want to carry it along in
> > the long run)
>
> We tend to not remove things unless we are absolutely certain nobody uses
> it, so probably making it built-in would be preferrable. I don't think
> show-index is used very often if ever, but scripts that use hash-object
> would use it really often and would do so via its --stdin interface if it
> knows that it is creating more than a dozen objects, so start-up time
> required to map the whole git is probably not an issue.
I do use it, but for developing/debugging pack stuff.
I don't suggest removing it, but I don't think making it a built-in has
value either.
So I really think that Linus' patch (which is missing hex.c btw) is a
good thing to do, even if only for the cleanup value.
Then, git-show-index could probably become test-show-index and no longer
leave the build directory.
Nicolas
next prev parent reply other threads:[~2010-01-22 2:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:37 Remove diff machinery dependency from read-cache Linus Torvalds
2010-01-21 20:07 ` Junio C Hamano
2010-01-21 20:15 ` Linus Torvalds
2010-01-21 22:18 ` Linus Torvalds
2010-01-21 23:25 ` Linus Torvalds
2010-01-22 0:45 ` Junio C Hamano
2010-01-22 0:59 ` Johannes Schindelin
2010-01-22 1:01 ` Junio C Hamano
2010-01-22 1:43 ` Johannes Schindelin
2010-01-22 3:50 ` Junio C Hamano
2010-01-22 2:20 ` Linus Torvalds
2010-01-22 2:25 ` Linus Torvalds
2010-01-22 3:50 ` Linus Torvalds
2010-01-22 8:43 ` Johannes Sixt
2010-01-22 11:47 ` [PATCH] merge-tree: remove unnecessary call of git_extract_argv0_path Johannes Sixt
2010-01-22 16:40 ` Linus Torvalds
2010-01-22 2:35 ` Nicolas Pitre [this message]
2010-01-22 2:44 ` Remove diff machinery dependency from read-cache Linus Torvalds
2010-01-22 3:56 ` Junio C Hamano
2010-01-22 4:21 ` Linus Torvalds
2010-01-22 4:31 ` Linus Torvalds
2010-01-22 3:58 ` Linus Torvalds
2010-01-23 6:31 ` Brian Campbell
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=alpine.LFD.2.00.1001212131230.1726@xanadu.home \
--to=nico@fluxnic.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.org \
/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).