From: Seth Falcon <sethfalcon@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: error with symlinks on OSX
Date: Thu, 15 Mar 2007 15:19:43 -0700 [thread overview]
Message-ID: <m2wt1i6tfk.fsf@ziti.local> (raw)
In-Reply-To: <20070315194410.GC29547@spearce.org> (Shawn O. Pearce's message of "Thu, 15 Mar 2007 15:44:10 -0400")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Seth Falcon <sethfalcon@gmail.com> wrote:
>> error: git-checkout-index: unable to create symlink Category/Makefile (Invalid argument)
>>
>> Now while my file system isn't smart enough to tell the difference
>> between t and T, it does support symlinks AFAIK.
>
> Yes, it does support symlinks. Is it possible that the name Category
> already existed, but as a file? Hmm.
I think in the revision before the update, there was a file
Category/Makefile and that it was replaced by a symlink.
So Category is/was a dir. Category/Makefile was a file and became a
symlink. Note that I am using git-svn to track an svn repository and
so the problem could be there.
However, I'm not sure where to look or what experiment to try next.
If I checkout an old revision prior to the file becoming a symlink and
then checkout master, I get:
git checkout -b foobar 74227bbd35a77b8
Switched to a new branch "foobar"
git checkout master
D Category/Makefile
[...snip...]
D vsn/Makefile
Switched to branch "master"
git reset --hard HEAD
error: git-checkout-index: unable to create symlink Category/Makefile (Invalid argument)
[...snip...]
error: git-checkout-index: unable to create symlink vsn/Makefile (Invalid argument)
HEAD is now at 30bd65d... the commit msg here
--
Seth
prev parent reply other threads:[~2007-03-15 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 17:12 error with symlinks on OSX Seth Falcon
2007-03-15 19:44 ` Shawn O. Pearce
2007-03-15 22:19 ` Seth Falcon [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wt1i6tfk.fsf@ziti.local \
--to=sethfalcon@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox