All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Freeman <jfreeman@cs.tamu.edu>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: clone fails: Could not get the current working directory
Date: Tue, 23 Sep 2008 09:45:57 -0500	[thread overview]
Message-ID: <48D90125.3090703@cs.tamu.edu> (raw)
In-Reply-To: <81b0412b0809230712u4a1cbe0fo69f558cbe9a26aae@mail.gmail.com>

Alex Riesen wrote:
> Saw them. .bashrc (/etc/bashrc too) is not used for non-interactive 
> sessions,
> like yours (of course, you can source them from
> .profile/.bash_login/.bash_profile).
>
> Have you tried the commands exactly? (Even more interesting would be to try
> a simple getpwd program which prints errno)
>   

I have.  I'm convinced that the problem is not missing commands; if it 
were, I'd be getting a "missing command," or "file not found," or 
similar error.  Like I've said, I am able to get this to work when the 
repo is in my home directory.  It only fails when the repo is on another 
path in the system for which I do not have read privileges all the way 
down - only at the end.

- John

  reply	other threads:[~2008-09-23 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21  0:49 clone fails: Could not get the current working directory John Freeman
     [not found] ` <d3a045300809211012l35b1ec2dq39f4174170d8c926@mail.gmail.com>
2008-09-21 22:18   ` John Freeman
2008-09-22 18:32     ` John Freeman
2008-09-23 12:39 ` Alex Riesen
2008-09-23 13:23   ` John Freeman
2008-09-23 14:12     ` Alex Riesen
2008-09-23 14:45       ` John Freeman [this message]
2008-09-23 15:01         ` Alex Riesen
2008-09-23 21:16           ` John Freeman
2008-09-24 11:30             ` Alex Riesen
2008-09-24 13:30               ` John Freeman
2008-09-24 14:43                 ` Alex Riesen

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=48D90125.3090703@cs.tamu.edu \
    --to=jfreeman@cs.tamu.edu \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.