Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Mike Coleman <tutufan@gmail.com>, junkio@cox.net
Subject: Re: [PATCH 2/2] Teach name-rev to identify revisions containing a certain blob
Date: Sat, 17 Feb 2007 10:30:50 -0800	[thread overview]
Message-ID: <7vire0tz51.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0702171838510.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Sat, 17 Feb 2007 18:39:50 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> +static struct object_hash file_trees = { 0, 0, NULL };
> +static struct object_array file_commits = { 0, 0, NULL };

These don't look good for two reasons: (1) you could leave BSS
to do the 0 initialization; (2) you need to change this if you
need to change the shape of "struct object_hash" later.

> +#define CONTAINS_FILE (1u<<10)

I am partly at fault, but I think we should have a consolidated
bit assignment policy in place before introducing new users of
object flags.  Some older code says in their comments that
revision.h reserves lower 8 bits while others say 16.  I offhand
know who is correct X-<.

  parent reply	other threads:[~2007-02-17 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 17:39 [PATCH 2/2] Teach name-rev to identify revisions containing a certain blob Johannes Schindelin
2007-02-17 18:24 ` Junio C Hamano
2007-02-17 23:52   ` Johannes Schindelin
2007-02-18  0:04   ` Johannes Schindelin
2007-02-17 18:30 ` Junio C Hamano [this message]
2007-02-17 23:31   ` Johannes Schindelin
2007-02-18  8:34 ` Junio C Hamano
2007-02-18  8:48   ` Junio C Hamano
2007-02-18 15:41   ` Johannes Schindelin

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=7vire0tz51.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=tutufan@gmail.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