From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC 4/6] object: add one bit to let creation of private types (OBJ_MAX + n)
Date: Sun, 22 Feb 2009 20:35:05 +0200 [thread overview]
Message-ID: <e29894ca0902221035s54e005adg586409754966cfcc@mail.gmail.com> (raw)
In-Reply-To: <7vocwuxrgb.fsf@gitster.siamese.dyndns.org>
Hi
On Sun, Feb 22, 2009 at 8:21 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Marc-André Lureau <marcandre.lureau@gmail.com> writes:
>
>> ---
>> object.h | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/object.h b/object.h
>> index 89dd0c4..83d3644 100644
>> --- a/object.h
>> +++ b/object.h
>> @@ -21,7 +21,7 @@ struct object_array {
>> } *objects;
>> };
>>
>> -#define TYPE_BITS 3
>> +#define TYPE_BITS 4
>> #define FLAG_BITS 27
>
> This would increase the value of (TYPE_BITS+FLAG_BITS). We spent a lot of
> effect to keep sizeof(struct object) to absolute minimum, and you need to
> have a very good reason if you are breaking it.
>
>
Ooops. Ok, I should try to think harder how to have my own tag_list. I
only store a struct tag or a struct light_tag currently.
One option is to reuse the struct tag, by adding a "light" flag, but I
am not fond of this idea.
Second option is to create a custom tag list in builtin-tag.c, not
reusing object_list. I guess this is better then. What do you think?
For example:
struct tag_list {
struct object *item;
int light; /* item is a struct light_tag */
struct object_list *next;
}
thanks,
--
Marc-André Lureau
Sent from: Helsinki Southern Finland Finland.
next prev parent reply other threads:[~2009-02-22 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 18:06 [PATCH/RFC 4/6] object: add one bit to let creation of private types (OBJ_MAX + n) Marc-André Lureau
2009-02-22 18:21 ` Junio C Hamano
2009-02-22 18:35 ` Marc-André Lureau [this message]
2009-02-23 1:47 ` 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=e29894ca0902221035s54e005adg586409754966cfcc@mail.gmail.com \
--to=marcandre.lureau@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).