From: Alexander Potashev <aspotashev@gmail.com>
To: daly@axiom-developer.org
Cc: git@vger.kernel.org
Subject: Re: builtin-add.c patch
Date: Wed, 10 Dec 2008 17:26:32 +0300 [thread overview]
Message-ID: <20081210142632.GA4137@myhost> (raw)
In-Reply-To: <200812101238.mBACcWQk023480@axiom-developer.org>
Hello, Tim!
On 06:38 Wed 10 Dec , daly@axiom-developer.org wrote:
> A trivial patch to fix a typo -- Tim Daly
>
>
> diff --git a/builtin-add.c b/builtin-add.c
> index ea4e771..5f2e68b 100644
> --- a/builtin-add.c
> +++ b/builtin-add.c
> @@ -23,7 +23,7 @@ static void fill_pathspec_matches(const char **pathspec, char *seen, int specs)
> int num_unmatched = 0, i;
>
> /*
> - * Since we are walking the index as if we are warlking the directory,
> + * Since we are walking the index as if we are walking the directory,
We probably should use subjunctive here:
"Since we are walking the index as if we _were_ walking the directory,".
Are there any native English speakers? :)
> * we have to mark the matched pathspec as seen; otherwise we will
> * mistakenly think that the user gave a pathspec that did not match
> * anything.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
It's also better to change the commit message, one should be able to
realize from it that the change is a typo fix in comments.
next prev parent reply other threads:[~2008-12-10 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 12:38 builtin-add.c patch daly
2008-12-10 14:26 ` Alexander Potashev [this message]
2008-12-10 16:01 ` Boyd Stephen Smith Jr.
2008-12-10 19:10 ` root
2008-12-10 22:27 ` [PATCH (resend)] Fix typo in comment in builtin-add.c Alexander Potashev
2008-12-10 23:38 ` Junio C Hamano
2008-12-10 19:14 ` builtin-add.c patch root
2008-12-10 20:10 ` Alexander Potashev
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=20081210142632.GA4137@myhost \
--to=aspotashev@gmail.com \
--cc=daly@axiom-developer.org \
--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).