+git@vger.kernel.org, plain text
I would say just use zsh globbing, it has the double star, but it'd
likely too late for that. You'd add a single rule: ignore any files
that are in a directory higher up than the .gitignore where the rule
is found.
Then if you have a git repo in your fs at /git/re
Stefan Beller writes:
> 2015-02-02 11:15 GMT-08:00 Junio C Hamano :
>
>> Isn't gitignore(5) documentation reasonably clear?
>> ...
>> - A leading slash matches the beginning of the pathname. For
>>example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".
>>
>>> That's true, though
2015-02-02 11:15 GMT-08:00 Junio C Hamano :
> Stefan Beller writes:
>
>> On 01.02.2015 14:51, /#!/JoePea wrote:
>>> I have this in my .gitignore:
>>>
>>> ./*.js
>>>
>>> I would expect that to cause git to ignore .js files in the same
>>> folder as .gitignore, but it doesn't do anything. However,
Stefan Beller writes:
> On 01.02.2015 14:51, /#!/JoePea wrote:
>> I have this in my .gitignore:
>>
>> ./*.js
>>
>> I would expect that to cause git to ignore .js files in the same
>> folder as .gitignore, but it doesn't do anything. However, this works:
>>
>> /*.js
>>
>> I'm not sure what
On 01.02.2015 14:51, /#!/JoePea wrote:
> I have this in my .gitignore:
>
> ./*.js
>
> I would expect that to cause git to ignore .js files in the same
> folder as .gitignore, but it doesn't do anything. However, this works:
>
> /*.js
>
> I'm not sure what this actually means because a leadi
I have this in my .gitignore:
./*.js
I would expect that to cause git to ignore .js files in the same
folder as .gitignore, but it doesn't do anything. However, this works:
/*.js
I'm not sure what this actually means because a leading slash is the
root of some filesystem, and we're not in t
6 matches
Mail list logo
