{"thread":{"id":"57783","subject":"Is it possible to treat symlinks just as normal files in Git?","startedAt":"2022-04-22T23:58:05Z","lastAt":"2022-04-22T23:58:05Z","messageCount":1,"participants":["Mikhail Merkuryev"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"454316","messageId":"9a1a7a84-76a6-c710-414d-fa566a3e0793@ukr.net","threadId":"57783","inReplyTo":null,"subject":"Is it possible to treat symlinks just as normal files in Git?","fromName":"Mikhail Merkuryev","fromEmail":"mercury13@ukr.net","sentAt":"2022-04-22T23:40:25Z","receivedAt":"2022-04-22T23:58:05Z","isPatch":false,"sender":{"key":"mercury13@ukr.net","avatar":null},"body":"My task. I have unit.h in both repo1 and repo2. I make a symlink from \nrepo1 to repo2 and want such a behaviour: in both repos I want to treat \nunit.h like normal file, not symlink.\n\nWhy to do this though Git has submodules?\n1. One of repos may be unrelated, private, corporate…\n2. Auxiliary things like unit testing require additional bookkeeping, \ne.g. moving unit testing framework (Google Test etc) to the submodule, \nspecial directory setup…\n3. The repo becomes harder to pick up if you do not have/want Git. With \nsubmodules, if you do “download ZIP”, you get uncompileable source. Even \nin Linux where Git is out-of-the-box, you do some command-line magic \nbefore repo starts to work.\n4. Submodules are just a “big gun” for library <30k in size.\n5. Developing alone does not involve pulling, but with submodules it \nbecomes the case.\n\nMen at Git for Windows thought it’s not just a Windows issue and sent me \nhere.\n"}]}