From: Junio C Hamano <gitster@pobox.com>
To: Josh Micich <josh.micich@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] improved validation of entry type in mktree
Date: Wed, 13 May 2009 23:24:55 -0700 [thread overview]
Message-ID: <7vd4acxkug.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <loom.20090514T051052-920@post.gmane.org> (Josh Micich's message of "Thu\, 14 May 2009 05\:11\:20 +0000 \(UTC\)")
Josh Micich <josh.micich@gmail.com> writes:
> diff --git a/builtin-mktree.c b/builtin-mktree.c
> index a56c917..a37954a 100644
> --- a/builtin-mktree.c
> +++ b/builtin-mktree.c
> @@ -71,7 +71,7 @@ static void mktree_line(char *buf, size_t len, int
> line_termination, int allow_m
> {
> char *ptr, *ntr;
> unsigned mode;
> - enum object_type type;
> + enum object_type mode_type;
Why?
> @@ -94,29 +94,37 @@ static void mktree_line(char *buf, size_t len, int
> line_termination, int allow_m
> if (S_ISGITLINK(mode))
> allow_missing = 1;
>
> - if (!allow_missing)
> - type = sha1_object_info(sha1, NULL);
> - else
> - type = object_type(mode);
> -
> - if (type < 0)
> - die("object %s unavailable", sha1_to_hex(sha1));
>
> *ntr++ = 0; /* now at the beginning of SHA1 */
> - if (type != type_from_string(ptr))
> - die("object type %s mismatch (%s)", ptr, typename(type));
>
> path = ntr + 41; /* at the beginning of name */
> + struct strbuf p_uq = STRBUF_INIT;
> if (line_termination && path[0] == '"') {
> - struct strbuf p_uq = STRBUF_INIT;
Why make its lifetime longer even though you do not use it outside of this
block?
> ...
> }
> +
> + mode_type = object_type(mode);
> + if (mode_type != type_from_string(ptr)) {
> + die("entry '%s' object type (%s) doesn't match mode type (%s)",
> path, ptr, typename(mode_type));
> + }
> +
> + enum object_type obj_type = sha1_object_info(sha1, NULL);
> + if (obj_type < 0) {
> + if (!allow_missing) {
This is the other way around; when allow_missing is given you shouldn't
even consult the object database to read it.
next prev parent reply other threads:[~2009-05-14 6:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 5:06 Proposed patch for mktree [0/3] Josh Micich
2009-05-14 5:09 ` [PATCH 1/3] '--missing' option for mktree: re-added strbuf_release(&p_uq), Updated man page Josh Micich
2009-05-14 6:04 ` Junio C Hamano
2009-05-14 19:44 ` Josh Micich
2009-05-14 5:10 ` [PATCH 2/3] added --batch option to mktree Josh Micich
2009-05-14 6:18 ` Junio C Hamano
2009-05-14 9:24 ` Josh Micich
2009-05-14 10:25 ` Sverre Rabbelier
2009-05-14 19:51 ` Josh Micich
[not found] ` <a644352c0905140217h382a4d18h988b229c12577de3@mail.gmail.com>
2009-05-15 8:31 ` Junio C Hamano
2009-05-14 5:11 ` [PATCH 3/3] improved validation of entry type in mktree Josh Micich
2009-05-14 6:24 ` Junio C Hamano [this message]
2009-05-14 22:46 ` Josh Micich
2009-05-14 22:49 ` Josh Micich
2009-05-15 6:23 ` Jakub Narebski
2009-05-15 16:57 ` Josh Micich
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=7vd4acxkug.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=josh.micich@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;
as well as URLs for NNTP newsgroup(s).