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

Re: Having Git follow symlinks

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jan 30, 2014, 12:37 UTC
Message-ID
<vpqa9ed1w8y.fsf@anie.imag.fr>
In-Reply-To
<alpine.DEB.2.00.1401300958320.30100@ds9.cixit.se>
Peter Krefting <peter@softwolves.pp.se> writes:
> Yeah, but then I have copies of the files, instead of having the files
> themselves under version control, meaning I need to copy them back to
> push changes back, or to merge them. That is undesirable :-/

One option is to have the symlink in the other direction: make /etc/foo a symlink to $GIT_WORKTREE/foo and version the later.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Christian CouderNext: Peter Krefting
Message 5 of 9 in “Having Git follow symlinks”
  1. Peter KreftingJan 28, 2014
  2. Johan HerlandJan 28, 2014
  3. Peter KreftingJan 30, 2014
  4. Christian CouderJan 30, 2014
  5. Matthieu MoyJan 30, 2014
  6. Peter KreftingJan 31, 2014
  7. Matthew RuffaloJan 31, 2014
  8. Junio C HamanoJan 31, 2014
  9. Matthieu MoyJan 31, 2014

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.