From: Jonathan Nieder <jrnieder@gmail.com>
To: Dmitry Ivankov <divanorama@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Shawn Pearce <spearce@spearce.org>
Subject: Re: [PATCH v2 2/3] fast-import: allow "merge $null_sha1" command
Date: Wed, 27 Jun 2012 16:33:55 -0500 [thread overview]
Message-ID: <20120627213355.GO12774@burratino> (raw)
In-Reply-To: <1340818825-13754-3-git-send-email-divanorama@gmail.com>
Dmitry Ivankov wrote:
> "from $null_sha1" and "merge $empty_branch" are already allowed so
> allow "merge $null_sha1" command too.
The reader might not realize that null_sha1 means
0000000000000000000000000000000000000000 until she reads the test
script. Is it possible to help her save time?
[...]
> --- a/fast-import.c
> +++ b/fast-import.c
> @@ -2631,12 +2631,14 @@ static struct hash_list *parse_merge(unsigned int *count)
> die("Mark :%" PRIuMAX " not a commit", idnum);
> hashcpy(n->sha1, oe->idx.sha1);
> } else if (!get_sha1(from, n->sha1)) {
> - unsigned long size;
> - char *buf = read_object_with_reference(n->sha1,
> - commit_type, &size, n->sha1);
> - if (!buf || size < 46)
> - die("Not a valid commit: %s", from);
> - free(buf);
> + if (!is_null_sha1(n->sha1)) {
> + unsigned long size;
> + char *buf = read_object_with_reference(n->sha1,
> + commit_type, &size, n->sha1);
> + if (!buf || size < 46)
> + die("Not a valid commit: %s", from);
> + free(buf);
> + }
Hm, ok. Maybe the "peel onion" call guarded by this "if" could be a
separate function to make this cleaner (and avoid some duplication of
code with other functions while at it)?
e.g.,
static int peel_to_commit(unsigned char sha1[20])
{
unsigned long size;
char *buf = read_object_with_reference(...);
if (!buf)
return -1;
free(buf);
if (size < strlen("commit ") + 40)
return -1;
return 0;
}
...
if (is_null_sha1(n->sha1))
; /* ok */
else if (peel_to_commit(n->sha1))
die("Not a valid commit: %s", from);
I like the direction, but as it is, this patch feels kind of "meh" to
me.
Thanks again and hope that helps,
Jonathan
next prev parent reply other threads:[~2012-06-27 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 17:40 [PATCH/RFC v2 0/3] fast-import: disallow empty branches as parents Dmitry Ivankov
2012-06-27 17:40 ` [PATCH v2 1/3] fast-import: do not write null_sha1 as a merge parent Dmitry Ivankov
2012-06-27 21:25 ` Jonathan Nieder
2012-07-24 19:30 ` Jonathan Nieder
2012-06-27 17:40 ` [PATCH v2 2/3] fast-import: allow "merge $null_sha1" command Dmitry Ivankov
2012-06-27 21:33 ` Jonathan Nieder [this message]
2012-06-27 22:30 ` Junio C Hamano
2012-06-27 23:39 ` Jonathan Nieder
2012-07-23 1:28 ` Jonathan Nieder
2012-06-27 17:40 ` [PATCH v2 3/3] fast-import: disallow "merge $itself" command Dmitry Ivankov
2012-06-27 21:22 ` Jonathan Nieder
2012-07-24 19:40 ` Jonathan Nieder
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=20120627213355.GO12774@burratino \
--to=jrnieder@gmail.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=srabbelier@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).