From: Junio C Hamano <gitster@pobox.com>
To: Thomas Harning <harningt@gmail.com>
Cc: git@vger.kernel.org, thomas.harning@trustbearer.com
Subject: Re: [PATCH] Converted git-merge-ours.sh -> builtin-merge-ours.c
Date: Fri, 23 Nov 2007 00:49:44 -0800 [thread overview]
Message-ID: <7voddluz13.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 4745E45C.7@gmail.com
Thomas Harning <harningt@gmail.com> writes:
> Here's a simple patch to make git-merge-ours.sh into a builtin.
>
> I figure this would be a simple way of getting in the git-development flow.
>
> Signed-off-by: Thomas Harning Jr <harningt@gmail.com>
Have you tried to read this proposed commit log message in the
context of "git log", after applying it on top of 'master'?
"Here's a simple patch to" and "I figure ..." are of not much
use.
The patch looks good except for minor style nits.
> diff --git a/builtin-merge-ours.c b/builtin-merge-ours.c
> new file mode 100644
> index 0000000..fbfe183
> --- /dev/null
> +++ b/builtin-merge-ours.c
> @@ -0,0 +1,32 @@
> +/*
> + * Implementation of git-merge-ours.sh as builtin
> + *
Traling whitespace.
> +int cmd_merge_ours(int argc, const char **argv, const char *prefix)
> +{
> + const char *nargv[] = {
> + "diff-index",
> + "--quiet",
> + "--cached",
> + "HEAD",
> + NULL
> + };
> + int i;
> +
> + int ret = cmd_diff_index(4, nargv, prefix);
> + printf("GOT: %i\n", ret);
Unused variable "i".
An unwanted blank line still in the sequence of variable
definitions, and a missing blank line after the definitions.
A leftover debug printf() is not very welcomed.
[Not a nit but a comment]
The call to cmd_diff_index() here raised my eyebrow a
bit. I would have skipped all the parameter parsing and
arranged it to directly call into run_diff_index()
instead.
As the result of literally translating the scripted
version of git-merge-ours, the code inherits a
corner-case bug. Can you spot it?
> + /* We need to exit with 2 if the index does not match our HEAD tree,
> + * because the current index is what we will be committing as the
> + * merge result.
> + */
We tend to format a multi-line comment block as:
/*
* We need to ...
* ... merge result.
*/
> + if(ret) ret = 2;
A SP between "if" and "("; put the body of the "if" on a
separate line.
Thanks. No need to resend; all these minor nits can be fixed
here easily.
next prev parent reply other threads:[~2007-11-23 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 20:19 [PATCH] Converted git-merge-ours.sh -> builtin-merge-ours.c Thomas Harning
2007-11-23 8:49 ` Junio C Hamano [this message]
2007-11-23 9:42 ` Jakub Narebski
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=7voddluz13.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=harningt@gmail.com \
--cc=thomas.harning@trustbearer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.