Re: Expected behavior of "git check-ignore"...

2017-07-30 Thread Philip Oakley
From: "Junio C Hamano" Sent: Thursday, July 27, 2017 6:05 PM John Szakmeister writes: On Mon, Jul 24, 2017 at 3:23 PM, Junio C Hamano wrote: [snip] I am reasonably sure that the command started its life as a pure debugging aid.

Re: Expected behavior of "git check-ignore"...

2017-07-27 Thread Junio C Hamano
John Szakmeister writes: > On Mon, Jul 24, 2017 at 3:23 PM, Junio C Hamano wrote: > [snip] >> I am reasonably sure that the command started its life as a pure >> debugging aid. >> >> The treatment of the negation _might_ impose conflicting goals to >>

Re: Expected behavior of "git check-ignore"...

2017-07-27 Thread John Szakmeister
On Mon, Jul 24, 2017 at 3:23 PM, Junio C Hamano wrote: [snip] > I am reasonably sure that the command started its life as a pure > debugging aid. > > The treatment of the negation _might_ impose conflicting goals to > its purpose as a debugging aid---a user who debugs his

Re: Expected behavior of "git check-ignore"...

2017-07-24 Thread Junio C Hamano
John Szakmeister writes: > Correct, it appears that if any line in the ignore matches, then it > exits with 0. So it's not that it's ignored, but that there is a > matching line in an ignore file somewhere. I can see the logic in > this if it's meant to be a debugging

Re: Expected behavior of "git check-ignore"...

2017-07-24 Thread John Szakmeister
On Sun, Jul 23, 2017 at 12:33 PM, Philip Oakley wrote: [snip] >> >> >> git init . >> echo 'foo/*' > .gitignore >> echo '!foo/bar' > .gitignore > > > Is this missing the >> append to get the full two line .gitignore? > adding in a `cat .gitignore` would help check. Yes,

Re: Expected behavior of "git check-ignore"...

2017-07-23 Thread Philip Oakley
ed git add's behavior. It turns out that it doesn't. If there is a negation rule, we end up returning that exclude and printing it and exiting with 0 (there are some ignored files) even though the file has been marked to not be ignored. Is the expected behavior of "git check-ignore" t

Expected behavior of "git check-ignore"...

2017-07-20 Thread John Szakmeister
turning that exclude and printing it and exiting with 0 (there are some ignored files) even though the file has been marked to not be ignored. Is the expected behavior of "git check-ignore" to return 0 even if the file is not ignore when a negation is present? >>>> git init