Re: Change in .gitignore handling: intended or bug?

2016-03-04 Thread Charles Strahan
The fix on my side was quite easy (and my .gitignore is probably a _lot_ hairier than most), and as Duy suggests, I think the new behavior makes a bit more sense. Personally, I would be pleased with keeping the new behavior, and chalking it up to an unintentional bug fix (the best kind). Either wa

Re: Change in .gitignore handling: intended or bug?

2016-03-03 Thread Charles Strahan
, 2016, at 12:51 AM, Kevin Daudt wrote: > On Thu, Mar 03, 2016 at 09:11:56PM -0500, Charles Strahan wrote: > > Hello, > > > > I've found a change in the way .gitignore works, and I'm not sure if > > it's a bug > > or intended. > > > >

Change in .gitignore handling: intended or bug?

2016-03-03 Thread Charles Strahan
Hello, I've found a change in the way .gitignore works, and I'm not sure if it's a bug or intended. Previously, one could use the following .gitignore: * !/foo !/foo/bar.txt !/baz !/baz/quux !/baz/quux/**/* And these files would be seen by git: foo/bar.txt baz/q