From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Martin Koegler <mkoegler@auto.tuwien.ac.at>, git@vger.kernel.org
Subject: Re: [PATCH] receive-pack: check object type of sha1 before using them as commits
Date: Wed, 02 Jan 2008 14:57:35 -0800 [thread overview]
Message-ID: <7vprwjvns0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0801021418510.3010@woody.linux-foundation.org> (Linus Torvalds's message of "Wed, 2 Jan 2008 14:21:51 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, 2 Jan 2008, Martin Koegler wrote:
>>
>> - old_commit = (struct commit *)parse_object(old_sha1);
>> - new_commit = (struct commit *)parse_object(new_sha1);
>> + old_object = parse_object(old_sha1);
>> + new_object = parse_object(new_sha1);
>
> I think it would be better to use
>
> old_object = lookup_commit_reference(old_sha1);
> if (!old_object)
> return "bad ref";
> new_object = lookup_commit_reference(new_sha1);
> if (!new_object)
> return "bad ref";
>
> which will write a slightly more useful error message if it's not a commit
> (ie it will use the "check_commit()" function in commit.c)
Hmmm... Three points.
* lookup_commit_reference() is silent if the object pointed at
by old/new SHA-1 is missing.
* when storing in refs/heads, we do not want to have committish
but we do want an actual commit object.
* returning like that the user cannot tell which ref had the
error.
prev parent reply other threads:[~2008-01-02 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 7:39 [PATCH] receive-pack: check object type of sha1 before using them as commits Martin Koegler
2008-01-02 22:21 ` Linus Torvalds
2008-01-02 22:57 ` 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=7vprwjvns0.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).