From: Alex Riesen <raa.lkml@gmail.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/5] pretty describe: add name info to struct commit
Date: Sun, 4 Nov 2007 15:07:00 +0100 [thread overview]
Message-ID: <20071104140700.GB3078@steel.home> (raw)
In-Reply-To: <472DB186.9030909@lsrfire.ath.cx>
René Scharfe, Sun, Nov 04, 2007 12:48:22 +0100:
> diff --git a/commit.h b/commit.h
> index b661503..80e94b9 100644
> --- a/commit.h
> +++ b/commit.h
> @@ -18,6 +18,9 @@ struct commit {
> struct commit_list *parents;
> struct tree *tree;
> char *buffer;
> + char *name;
> + unsigned int name_flags;
> + char name_prio;
> };
It increases size of struct commit by ~12 bytes (assuming 4byte
allignment), and this is a popular structure. Besides, the three new
fields used by only git-describe, which nobody has in their top-ten
used commands (see "best git practices" thread). If the fields are so
badly needed (and the information can't (really?) be stored somewhere
else), maybe they could be at least compressed when not used:
struct commit_name_info {
unsigned int name_flags;
char name_prio;
char name[FLEX_ARRAY];
};
struct commit {
struct commit_list *parents;
struct tree *tree;
char *buffer;
struct commit_name_info *name_info;
};
BTW, do we still have some bits left in struct object->flags?
To, for example, switch between normal and expanded structure of
second-level object (i.e. commit and commit-with-names).
next prev parent reply other threads:[~2007-11-04 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 11:48 [PATCH 1/5] pretty describe: add name info to struct commit René Scharfe
2007-11-04 14:07 ` Alex Riesen [this message]
2007-11-04 14:22 ` Johannes Schindelin
2007-11-04 15:06 ` René Scharfe
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=20071104140700.GB3078@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).