git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Potashev <aspotashev@gmail.com>
To: A S Potashev <aspotashev@gmail.com>
Cc: Alexander Potashev <aspotashev@gmail.com>,
	"Boyd Stephen Smith Jr." <bss03@volumehost.net>,
	Junio C Hamano <gitster@pobox.com>, <git@vger.kernel.org>
Subject: [PATCH (resend)] Fix typo in comment in builtin-add.c
Date: Thu, 11 Dec 2008 01:27:44 +0300	[thread overview]
Message-ID: <1228948064-4006-1-git-send-email-aspotashev@gmail.com> (raw)
In-Reply-To: <200812101910.mBAJAsF04710@localhost.localdomain>

Reported-by: Tim Daly <daly@axiom-developer.org>
Cc: Boyd Stephen Smith Jr. <bss03@volumehost.net>
Cc: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Signed-off-by: Alexander Potashev <aspotashev@gmail.com>
---
 builtin-add.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/builtin-add.c b/builtin-add.c
index ea4e771..719de8b 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 were walking the directory,
 	 * 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.
-- 
1.6.0.4

  reply	other threads:[~2008-12-10 22:28 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
2008-12-10 16:01   ` Boyd Stephen Smith Jr.
2008-12-10 19:10   ` root
2008-12-10 22:27     ` Alexander Potashev [this message]
2008-12-10 23:38       ` [PATCH (resend)] Fix typo in comment in builtin-add.c 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=1228948064-4006-1-git-send-email-aspotashev@gmail.com \
    --to=aspotashev@gmail.com \
    --cc=bss03@volumehost.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).