From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Gabriel Souza Franco <gabrielfrancosouza@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: [PATCH v2] fetch-pack: fix object_id of exact sha1
Date: Mon, 29 Feb 2016 09:30:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1602290912260.3152@virtualbox> (raw)
In-Reply-To: <1456698144-11519-1-git-send-email-gabrielfrancosouza@gmail.com>
Hi Gabriel,
On Sun, 28 Feb 2016, Gabriel Souza Franco wrote:
> Not the cleanest conditional I've ever written, but it should handle
> all cases correctly.
It could be much worse:
> + if (get_oid_hex(name, &oid) ||
> + (name[GIT_SHA1_HEXSZ] != ' ' &&
> + name[GIT_SHA1_HEXSZ] != '\0'))
I know developers who would write this as
if (get_oid_hex(name, &oid) || (name[GIT_SHA1_HEXSZ] & ' '))
and not even begin to realize that this is a problem.
So I'd say your conditional is good.
Having said that, this *might* be a good opportunity to imitate the
skip_prefix() function. If there are enough similar code constructs, we
could simplify all of them by introducing the function
skip_oid_hex(const char *str, struct object_id *oid, const char **out)
that returns 1 if and only if an oid was parsed, and stores the pointer
after the oid in "out" (skipping an additional space if there is one)?
Ciao,
Dscho
next prev parent reply other threads:[~2016-02-29 8:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 12:43 [PATCH] fetch-pack: fix unadvertised requests validation Gabriel Souza Franco
2016-02-27 18:25 ` Junio C Hamano
2016-02-27 18:32 ` Junio C Hamano
2016-02-27 18:38 ` Junio C Hamano
2016-02-27 19:07 ` Jeff King
2016-02-27 19:19 ` Jeff King
2016-02-27 20:28 ` Gabriel Souza Franco
2016-02-27 20:32 ` [PATCH] fetch-pack: fix object_id of exact sha1 Gabriel Souza Franco
2016-02-27 22:12 ` Jeff King
2016-02-27 22:23 ` Gabriel Souza Franco
2016-02-28 19:29 ` Junio C Hamano
2016-02-28 22:22 ` [PATCH v2] " Gabriel Souza Franco
2016-02-29 8:30 ` Johannes Schindelin [this message]
2016-02-29 10:00 ` Jeff King
2016-03-01 2:08 ` Gabriel Souza Franco
2016-03-01 2:12 ` [PATCH v3] " Gabriel Souza Franco
2016-03-01 4:54 ` Jeff King
2016-03-03 23:35 ` Gabriel Souza Franco
2016-03-04 0:50 ` Jeff King
2016-03-05 1:11 ` [PATCH v4] " Gabriel Souza Franco
2016-03-05 16:59 ` Jeff King
2016-03-05 18:54 ` Junio C Hamano
2016-03-05 19:34 ` [PATCH] fetch-pack: update the documentation for "<refs>..." arguments Gabriel Souza Franco
2016-03-05 19:35 ` Junio C Hamano
2016-03-01 4:40 ` [PATCH v2] fetch-pack: fix object_id of exact sha1 Jeff King
2016-02-29 9:50 ` [PATCH] " Jeff King
2016-02-27 22:08 ` [PATCH] fetch-pack: fix unadvertised requests validation Jeff King
2016-02-28 19:14 ` 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=alpine.DEB.2.20.1602290912260.3152@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=gabrielfrancosouza@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).