Re: [PATCH] config: add conditional include
- From
Jeff King <peff@peff.net>
- Date
- Jun 27, 2016, 16:35 UTC
- Message-ID
- <20160627163559.GA5296@sigill.intra.peff.net>
- In-Reply-To
- <CACsJy8D6TxkMWJTUCeDd8tuMyTRXcvWdMw4VL3nO7jbLEgjE-A@mail.gmail.com>
On Mon, Jun 27, 2016 at 06:32:39PM +0200, Duy Nguyen wrote:
Show 18 quoted lines
> On Mon, Jun 27, 2016 at 6:20 PM, Jeff King <peff@peff.net> wrote: > > You do allow distinguishing the suffix thing with "/" at the end in the > > rule above, though. So between the two rules: > > > > - slash at the end is a shorthand for "/**" > > > > - no-slash at the beginning (i.e., a non-absolute path) is a shorthand > > for "**/" at the beginning > > Neither slash or "./" at the beginning... > > > you should be able to specify anything. > > ...then yeah it looks pretty good. With the exception of "./" we can > still have paths relative to where the the config file is. For > $HOME/.gitconfig that eliminates the need for expanding "~" > ($HOME/.config/git/config may still need it, unless we allow "../" > too, but that complicates matching).
Yeah, I didn't think actual relative paths were that interesting, but if we declare that they are relative to the config file, I agree that works pretty well. And I agree that "./" is a convenient way to anchor them.
-Peff