Re: .gitattributes override behavior (possible bug, or documentation bug)
- From
- Dakota Hawkins <dakota@dakotahawkins.com>
- Date
- Mar 21, 2018, 08:35 UTC
- Message-ID
- <CAHnyXxTP7i4G=4G_ihRQTSbLNzAWuqZ3FoX0NtesAX219Pa5-g@mail.gmail.com>
- In-Reply-To
- <20180321075041.GA24701@sigill.intra.peff.net>
> I think it means "for the rest of the description of how the patterns > work". I.e., "foo/" matches as "foo" when the rest of the matching rules > are applied. I agree it's a bit awkward. Patches welcome. :)
I'd be more than happy to do that!
It will take me a while, this (email and text-patches) is foreign to me and will take me some extra time, but I think I can figure it out.
Is "consistent with the way how pathspec works in general in Git" absolutely still true (and relevant?)