From: Matthias Lederhofer <matled@gmx.net>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
Cc: git@vger.kernel.org
Subject: Re: git-sh-setup.sh:cd_to_toplevel problematic with symlinks
Date: Tue, 7 Aug 2007 12:11:56 +0200 [thread overview]
Message-ID: <20070807101155.GA19233@moooo.ath.cx> (raw)
In-Reply-To: <20070806211238.GA27363@informatik.uni-freiburg.de>
Your mail did not make it to the list, therefore I quote the full
mail.
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de> wrote:
> Matthias Lederhofer wrote:
> > cd_to_toplevel takes the output of git rev-parse --show-cdup and feeds
> > it to cd. The problem is that cd uses PWD to do what the user means
> > when saying cd .., i.e. it goes to /foo when in /foo/bar even though
> > /foo/bar might be a symlink. Example:
> >
> > (in an existing git repository)
> > /tmp/foo$ mkdir -p a/b
> > /tmp/foo$ ln -s a/b c
> > /tmp/foo$ cd c
> > /tmp/foo/c$ git fetch . master:master
> > git-fetch: line 108: /FETCH_HEAD: Permission denied
> >
> > Is there any way to tell cd to ignore $PWD?
> cd -P ... does the trick. IIRC it's in SUSv3, but once more, Solaris
> /bin/sh doesn't know about that option:
>
> login@~ > uname -a
> SunOS login 5.10 Generic_125100-10 sun4u sparc
>
> login@~ > /bin/sh
>
> $ mkdir /tmp/foo; cd /tmp/foo
>
> $ git init
> Initialized empty Git repository in .git/
>
> $ mkdir -p a/b; ln -s a/b c; cd c
>
> $ git rev-parse --show-cdup
> ../../
>
> $ cd -P ../../
> -P: does not exist
Do we care about that shell? There was another thread about shell
script cleanup where the default sun /bin/sh doesn't support some
other features from the git shell scripts too.
next prev parent reply other threads:[~2007-08-07 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 16:10 git-sh-setup.sh:cd_to_toplevel problematic with symlinks Matthias Lederhofer
[not found] ` <20070806211238.GA27363@informatik.uni-freiburg.de>
2007-08-07 10:11 ` Matthias Lederhofer [this message]
2007-08-07 12:45 ` Uwe Kleine-König
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=20070807101155.GA19233@moooo.ath.cx \
--to=matled@gmx.net \
--cc=git@vger.kernel.org \
--cc=ukleinek@informatik.uni-freiburg.de \
/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;
as well as URLs for NNTP newsgroup(s).