From: John Keeping <john@keeping.me.uk>
To: Philip Oakley <philipoakley@iee.org>
Cc: Ville Walveranta <walveranta@gmail.com>, git@vger.kernel.org
Subject: Re: Git 1.8.4.2: 'git-rev-parse --is-inside-git-dir' wrong output!
Date: Sat, 2 Nov 2013 14:06:57 +0000 [thread overview]
Message-ID: <20131102140656.GE24023@serenity.lan> (raw)
In-Reply-To: <11593D3DCFCD4D24BB881B9E5FAB79C0@PhilipOakley>
On Sat, Nov 02, 2013 at 01:47:02PM -0000, Philip Oakley wrote:
> From: "John Keeping" <john@keeping.me.uk>
> Sent: Saturday, November 02, 2013 10:58 AM
> > On Fri, Nov 01, 2013 at 06:19:51PM -0500, Ville Walveranta wrote:
> >> "git-rev-parse --is-inside-git-dir" outputs "fatal: Not a git
> >> repository (or any of the parent directories): .git", instead of
> >> "false" when outside of a git directory. "--is-inside-work-tree"
> >> behaves the same way. Both commands work correctly (i.e. output
> >> "true") when inside a git directory, or inside a work tree,
> >> respectively.
> >
> > I think that's intentional - and it looks like the behaviour has not
> > changed since these options were added. With the current behaviour
> > you
> > get three possible outcomes from "git
> > rev-parse --is-inside-work-tree":
> >
> > if worktree=$(git rev-parse --is-inside-work-tree 2>/dev/null)
> > then
> > if test "$worktree" = true
> > then
> > echo 'inside work tree'
> > else
> > echo 'in repository, but not in work tree'
> > fi
> > else
> > echo 'not in repository'
> > fi
> > --
>
>
> Shouldn't this case which produces "fatal:..." need to be documented in
> the man page?
> https://www.kernel.org/pub/software/scm/git/docs/git-rev-parse.html
> doesn't mention it.
I'm not sure where it should go in there. The documentation for
--git-dir says:
If $GIT_DIR is not defined and the current directory is not detected
to lie in a Git repository or work tree print a message to stderr and
exit with nonzero status.
but there reality is that if you do not specify --parseopt or --sq-quote
then the command expects to be run in a Git repository [1], so perhaps
it would be better to say something under "Operation Modes" or in the
description.
[1] After taking account of $GIT_DIR, $GIT_WORK_TREE, and arguments to
the base "git" driver that affect these variables.
next prev parent reply other threads:[~2013-11-02 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 23:19 Git 1.8.4.2: 'git-rev-parse --is-inside-git-dir' wrong output! Ville Walveranta
2013-11-02 10:24 ` Øystein Walle
2013-11-02 10:58 ` John Keeping
2013-11-02 13:47 ` Philip Oakley
2013-11-02 14:06 ` John Keeping [this message]
2013-11-02 17:03 ` Philip Oakley
2013-11-02 19:42 ` Ville Walveranta
2013-11-02 20:20 ` John Keeping
2013-11-02 22:58 ` Ville Walveranta
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=20131102140656.GE24023@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=walveranta@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.