From: Bryan Turner <bturner@atlassian.com>
To: Daniel Malendez <dmalendez@googlemail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Git doesn't support symlinks
Date: Wed, 25 Mar 2020 17:23:01 -0700 [thread overview]
Message-ID: <CAGyf7-FF0aEEiRGjZ_+RuyYnSV5cYn+-Hp5q7dZRADj_VL034g@mail.gmail.com> (raw)
In-Reply-To: <CA8EDABA-A41C-4177-A149-51DCD07C319C@googlemail.com>
On Wed, Mar 25, 2020 at 4:38 PM Daniel Malendez
<dmalendez@googlemail.com> wrote:
>
> Hi everyone,
>
> I use `Ubuntu 18.04` with filesystem `ext` and `git 2.26.0`. I want to add a macOS Framework to my git repo, which fails with the following error message:
>
> $ git add -f /var/opt/project1/Foo.framework/Headers/Interior.h
> fatal: pathspec '/var/opt/project1/Foo.framework/Headers/Interior.h' is beyond a symbolic link
>
> If I use `$ git add .` it works fine. Is this a bug? This is what `ls` returns
>
> Foo.framework $ ls -l
> lrwxr-xr-x Headers -> Versions/Current/Headers
> lrwxr-xr-x Resources -> Versions/Current/Resources
> drwxr-xr-x Versions
This didn't add the same thing. What does a "git status" show at this
point? I'd expect it would show "Versions/Current/Headers/interior.h"
as added to the index, not "Headers/interior.h".
>
> This sounds like a bug, correct? If not, I am thankful for any advice! Thanks!
>
It doesn't necessarily seem like a bug, to me; more like a case where
Git could potentially be "smarter" to try and determine that, while
"Headers/interior.h" is beyond a symlink, the target of that symlink
is still in the repository. (Versions/Current _is_ in the same
repository, right?)
>
>
>
> Best Regards,
> Daniel
next prev parent reply other threads:[~2020-03-26 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 23:38 Git doesn't support symlinks Daniel Malendez
2020-03-26 0:23 ` Bryan Turner [this message]
[not found] ` <D3B355BB-BB09-4AA7-8D8A-58B61529D617@googlemail.com>
2020-03-26 0:37 ` Daniel Malendez
2020-03-26 0:50 ` Danh Doan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGyf7-FF0aEEiRGjZ_+RuyYnSV5cYn+-Hp5q7dZRADj_VL034g@mail.gmail.com \
--to=bturner@atlassian.com \
--cc=dmalendez@googlemail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).