git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] diff.c: return filepair from diff_unmerge()
Date: Sun, 24 Apr 2011 18:18:41 -0700	[thread overview]
Message-ID: <7vtydnku1a.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <BANLkTi=fnzRVc8Lx_Wba4yqa7u8t3xGAtQ@mail.gmail.com> (Thiago Farina's message of "Sun, 24 Apr 2011 19:18:35 -0300")

Thiago Farina <tfransosi@gmail.com> writes:

> Some unrelated style comments below.
> ...
>> -void diff_unmerge(struct diff_options *options,
>> -                 const char *path,
>> -                 unsigned mode, const unsigned char *sha1)
>> +struct diff_filepair *diff_unmerge(struct diff_options *options,
>> +                                  const char *path,
>> +                                  unsigned mode, const unsigned char *sha1)
>>  {
>
> While you are here, why not write one arg per line?

No, actually I reindented the two lines by accident; I didn't mean to.

>> diff --git a/diff.h b/diff.h
>> index bf2f44d..f51a8ee 100644
>> --- a/diff.h
>> +++ b/diff.h
>> @@ -209,7 +209,7 @@ extern void diff_change(struct diff_options *,
>>                        const char *fullpath,
>>                        unsigned dirty_submodule1, unsigned dirty_submodule2);
>>
>> -extern void diff_unmerge(struct diff_options *,
>> +extern struct diff_filepair *diff_unmerge(struct diff_options *,
>
> While you are here, why not add the argument name |options| here too?
>
>>                         const char *path,
>>                         unsigned mode,
>>                         const unsigned char *sha1);

The patch was meant to be minimum to begin with.  Besides, there is no
risk of confusion from not naming the option in this case, so even if we
were shooting for clean-up, we wouldn't be adding such noise here.  The
other parameters do benefit from descriptive names, so there is no need to
remove the names either.

In other case, your "why not" is totally unwarranted for this hunk.

  reply	other threads:[~2011-04-25  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 20:51 [PATCH 0/4] Fix diff-files output for unmerged paths Junio C Hamano
2011-04-24 20:51 ` [PATCH 1/4] test: use $_z40 from test-lib Junio C Hamano
2011-04-24 20:51 ` [PATCH 2/4] diff.c: return filepair from diff_unmerge() Junio C Hamano
2011-04-24 22:18   ` Thiago Farina
2011-04-25  1:18     ` Junio C Hamano [this message]
2011-04-24 20:51 ` [PATCH 3/4] diff: remove often unused parameters " Junio C Hamano
2011-04-24 20:51 ` [PATCH 4/4] diff-files: show unmerged entries correctly Junio C Hamano
2011-04-24 20:53 ` [PATCH] Fix "add -u" that sometimes fails to resolve unmerged paths 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=7vtydnku1a.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=tfransosi@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).