From: Eric Sunshine <sunshine@sunshineco.com>
To: babourn <ba.bourn@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2][GSoC 2014] diff: used is_dot_or_dotdot() in code
Date: Tue, 18 Mar 2014 23:45:42 -0400 [thread overview]
Message-ID: <CAPig+cSxu1WAEg7YmnNn-kHZMj4AacRaVPMthgAwFN0GmrrYCg@mail.gmail.com> (raw)
In-Reply-To: <1395192636735-7605956.post@n2.nabble.com>
On Tue, Mar 18, 2014 at 9:30 PM, babourn <ba.bourn@gmail.com> wrote:
> Subject: diff: used is_dot_or_dotdot() in code
Use imperative voice: "use" rather than "used"
> in accordance with the GSoC Microproject implemented
This commentary will not have much meaning to someone reading the
commit log months or years from now. Place it below the "---" line
following your sign-off.
> the call is_dot_or_dotdot() in the code in order to
> further universalize the call to the function and
> increase code continuity.
It should be sufficient to explain the patch by just saying:
Subject: replace manual "."/".." check with is_dot_or_dotdot()
The rest of the explanatory text can be dropped since it doesn't add
anything (meaningful) beyond what the subject says.
> Signed-off-by: Brian Bourn <bab2177@columbia.edu>
> ---
> diff-no-index.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/diff-no-index.c b/diff-no-index.c
> index ba915af..44cce25 100644
> --- a/diff-no-index.c
> +++ b/diff-no-index.c
> @@ -26,7 +26,7 @@ static int read_directory_contents(const char *path,
> struct string_list *list)
> return error("Could not open directory %s", path);
>
> while ((e = readdir(dir)))
> - if (strcmp(".", e->d_name) && strcmp("..", e->d_name))
> + if (!is_dot_or_dotdot(e->d_name))
The patch is severely whitespace-damaged. (Did you post it through Nabble?)
> string_list_insert(list, e->d_name);
>
> closedir(dir);
> --
> 1.9.0
>
>
>
> --
> View this message in context: http://git.661346.n2.nabble.com/PATCH-GSoC-2014-diff-Imported-dir-h-and-renamed-read-directory-tp7605950p7605956.html
> Sent from the git mailing list archive at Nabble.com.
> --
next prev parent reply other threads:[~2014-03-19 3:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 0:35 [PATCH] [GSoC 2014]diff: Imported dir.h and renamed read_directory() Brian Bourn
2014-03-19 1:19 ` Eric Sunshine
2014-03-19 1:30 ` [PATCH 2/2][GSoC 2014] diff: used is_dot_or_dotdot() in code babourn
2014-03-19 3:45 ` Eric Sunshine [this message]
[not found] ` <CAM+=D-CO9A4hYb+9tVf_cAOMqkTm3taBLPp0eHtFkuMUCFw2ng@mail.gmail.com>
2014-03-19 4:08 ` Eric Sunshine
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=CAPig+cSxu1WAEg7YmnNn-kHZMj4AacRaVPMthgAwFN0GmrrYCg@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=ba.bourn@gmail.com \
--cc=git@vger.kernel.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).