From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Add specialized object allocator
Date: Mon, 19 Jun 2006 14:38:45 -0700 [thread overview]
Message-ID: <7vhd2g966y.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0606191327240.5498@g5.osdl.org> (Linus Torvalds's message of "Mon, 19 Jun 2006 13:30:29 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Mon, 19 Jun 2006, Junio C Hamano wrote:
>>
>> Impressed. I wonder if we want to deal with any_object
>> structure as well.
>
> Well, it would certainly be very easily doable, but none of the core code
> actually uses it, so it wasn't even on my radar.
I think the definition of "the core" in your earlier message was
"stuff I [jc: Linus] use myself", and I think the above
statement is in line with that definition.
It is hereby officially declared that commit walkers are not
part of the core ;-).
Even the commit walker uses lookup_unknown only for the starting
object and all the rest are of known type, so it does not help
even if we did "union any_object" that much.
prev parent reply other threads:[~2006-06-19 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 17:44 Add specialized object allocator Linus Torvalds
2006-06-19 18:10 ` Linus Torvalds
2006-06-19 19:44 ` Junio C Hamano
2006-06-19 20:30 ` Linus Torvalds
2006-06-19 21:38 ` Junio C Hamano [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=7vhd2g966y.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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