git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Rusty Dog Ink <chris@rustydogink.com>
Cc: git@vger.kernel.org
Subject: Re: A little help with error?
Date: Wed, 10 Aug 2011 06:21:21 -0600	[thread overview]
Message-ID: <20110810122121.GB17071@sigill.intra.peff.net> (raw)
In-Reply-To: <752985D1B23046F994920F9018B53DF8@rustydogink.com>

On Sun, Aug 07, 2011 at 02:16:57PM -0700, Rusty Dog Ink wrote:

> git add --force /Users/chris/Sites/mattSchubert/public/css/browserfix.css => "Crappy Error"
> Yields this error.
> fatal: '/Users/chris/Sites/mattSchubert/public/css/browserfix.css' is outside repository 

We can't say if this is reasonable or not without knowing more. Which
directory are you in? Which git repository do you expect to be found?
Which repository does git actually find (try "git rev-parse --git-dir")?
Do you have GIT_WORK_TREE set in the environment, or core.worktree set
in your config?

> This command does gives the same error. 
> git add --force /public/css/browserfix.css => "Same error"
> But this command, works. Why?
> git add --force public/css/browserfix.css => "Works yeah"

The top one seems nonsensical, unless your git repository is at one of:

  /.git
  /public/.git
  /public/css/.git

The bottom one makes sense; you are looking at files in the current
directory, which is going to be inside your repository (unless you are
setting some of worktree variables I mentioned above).

Are you trying to do something clever with symlinks to /public? If so,
show us.

-Peff

      reply	other threads:[~2011-08-10 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 21:16 A little help with error? Rusty Dog Ink
2011-08-10 12:21 ` Jeff King [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=20110810122121.GB17071@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=chris@rustydogink.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.
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).