git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Handling of paths

From
VTVictor Toni <victor.toni@gmail.com>
Date
Jul 19, 2017, 16:48 UTC
Message-ID
<CAG0OSgdEE3g-ugEJU4EZqfbxZ=3h2WPdLC4W4mG7b6UeTaXQ-Q@mail.gmail.com>
Hello,

I have a .gitconfig in which I try to separate work and private stuff by using includes which works great.

When using [include] the path is treated either
- relative to the including file (if the path itself relative)
- relative to the home directory if it starts with ~
- absolute if the path is absolute
This is fine and expected.

What's unexpected is that paths used for sslKey or sslCert are treated differently insofar as they are expected to be absolute. Relative paths (whether with or without "~") don't work.

It would't be an issue to use absoulte paths if I wouldn't use the same config for Linux and Windows and each OS has its own semantic where it $HOME ishould be.

To avoid double configurations I tried to use the same directory structure within my $HOME for both OS.

This approach fails since paths other than for [include] seem to have to be absolute which seems like a bug to me.

Do you have any suggestions how I could make this work?

Thank you, Victor

Next: Junio C Hamano
Message 1 of 8 in “Handling of paths”
  1. Victor ToniJul 19, 2017
  2. Junio C HamanoJul 20, 2017
  3. Charles BaileyJul 20, 2017
  4. Junio C HamanoJul 20, 2017
  5. Charles BaileyJul 20, 2017
  6. Victor ToniJul 20, 2017
  7. Junio C HamanoJul 21, 2017
  8. Jeff KingJul 24, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.