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

Re: [PATCH] RFC Optionally handle symbolic links as copies

From
Robin Rosenberg <robin.rosenberg@dewire.com>
Date
Dec 6, 2012, 11:51 UTC
Message-ID
<954603524.19440856.1354794705772.JavaMail.root@dewire.com>
In-Reply-To
<50C04255.8050209@viscovery.net>
----- Ursprungligt meddelande -----
Show 11 quoted lines
> Am 12/5/2012 23:46, schrieb Robin Rosenberg:
> > - git status - when do we report a diff.
> > 	- After checkout we should probably not
> 
> Are you saying that it should be ignored that the index records a
> symbolic
> link, but the worktree contains a regular file and that the regular
> file
> does not even contain the value of the symbolic link (like it would
> in the
> core.symlinks=false case)?

Well we should have some notion of clean state. That could be handled in more than one way. We could just ignore it, or compare the copy with the content of the link target. The first is good enough for a proof-of concept, but perhaps not as a solution since we don't have good other means to check that the copy is stale.

-- robin
Previous: Johannes Sixt
Message 8 of 8 in “RFC Optionally handle symbolic links as copies”
  1. RFC Optionally handle symbolic links as copiesRobin Rosenberg, Dec 5, 2012
  2. Junio C HamanoDec 5, 2012
  3. Robin RosenbergDec 6, 2012
  4. Michael J GruberDec 12, 2012
  5. Robin RosenbergDec 12, 2012
  6. Junio C HamanoDec 12, 2012
  7. Johannes SixtDec 6, 2012
  8. Robin RosenbergDec 6, 2012

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.