builtin-add.c patch

builtin-add.c patch

[daly]

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 have to mark the matched pathspec as seen; otherwise we will
 	 * mistakenly think that the user gave a pathspec that did not match
 	 * anything.

Re: builtin-add.c patch

[Alexander Potashev]

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.

Re: builtin-add.c patch

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Wednesday 2008 December 10 08:26:32 Alexander Potashev wrote:
>> 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? :)

Southern bah the grace o' gawd. :)

Yes, the subjunctive is the appropriate tense for use in hypotheticals ("as 
if").
-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: builtin-add.c patch

[root]

Alexander,

Feel free to change the patch.
Its hardly worth the bits of email used
but it does need to be fixed.

Tim

[PATCH (resend)] Fix typo in comment in builtin-add.c

[Alexander Potashev]

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

Re: [PATCH (resend)] Fix typo in comment in builtin-add.c

[Junio C Hamano]

Alexander Potashev <aspotashev@gmail.com> writes:

> 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>

Eek.  Why so many Cc: here for such a trivial patch?

Will apply, thanks.

Re: builtin-add.c patch

[root]

Alexander,

I saw a suggestion that git could be used as a filesystem rather
than as a code repository. I'm looking to convert it for this
purpose to sit underneath Axiom, a computer algebra system written
in common lisp. Basically the idea is that a "close" operation does
a 'git add foo ; git commit'. 

Are you aware of anyone who has used git as a filesystem?

Tim Daly

Re: builtin-add.c patch

[Alexander Potashev]

Hello, Tim!

On 14:14 Wed 10 Dec     , root wrote:
> Alexander,
> 
> I saw a suggestion that git could be used as a filesystem rather
> than as a code repository. I'm looking to convert it for this
> purpose to sit underneath Axiom, a computer algebra system written
> in common lisp. Basically the idea is that a "close" operation does
> a 'git add foo ; git commit'. 
> 
> Are you aware of anyone who has used git as a filesystem?
> 
> Tim Daly
> 

It's a quite off-topic question. But Git is not optimized to track
individual files with separate history
( see http://www.youtube.com/watch?v=8dhZ9BXQgc4 ).
Also, Git uses only 644 and 755 permissions (755 stands for
executables, often scripts - shell scripts, perl, ...), but
usual filesystems provide full range of premissions/ownership.

                                 Alexander