git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: [BUG] git --work-tree=... status
Date: Sun, 12 Aug 2007 20:58:56 +0200	[thread overview]
Message-ID: <20070812185855.GA16704@informatik.uni-freiburg.de> (raw)

Hello,

I don't have time now to look into it, so for now as usual just a
report.  If nobody takes it, I will do it later.

	zeisberg@cassiopeia:~/gsrc/git$ git version
	git version 1.5.3.rc4.887.gd56871c

[That's Junio's next + my doc change "checkout-index doc: use --work-dir in
the export example"]

	zeisberg@cassiopeia:~/gsrc/git$ mkdir export

	zeisberg@cassiopeia:~/gsrc/git$ git --work-tree=export checkout-index -a

	zeisberg@cassiopeia:~/gsrc/git$ git --work-tree=export status
	fatal: /home/zeisberg/usr/bin/git-status cannot be used without a working tree.

runstatus works as expected (at least after some thought):

	zeisberg@cassiopeia:~/gsrc/git$ git --work-tree=export runstatus | head
	# On branch next
	# Changed but not updated:
	#   (use "git add <file>..." to update what will be committed)
	#
	#       modified:   .gitignore
	#       modified:   .mailmap
	#       modified:   COPYING
	#       modified:   Documentation/.gitignore
	#       modified:   Documentation/Makefile
	#       modified:   Documentation/RelNotes-1.5.0.1.txt

The problem seems to be that require_work_tree demands more that I think
it should.  It calls `git rev-parse --is-inside-work-tree`.

Best regards
Uwe

-- 
Uwe Kleine-König

http://www.google.com/search?q=1+newton+in+kg*m+%2F+s%5E2

             reply	other threads:[~2007-08-12 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 18:58 Uwe Kleine-König [this message]
2007-08-12 19:32 ` [BUG] git --work-tree=... status Junio C Hamano
2007-08-17 11:50   ` 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=20070812185855.GA16704@informatik.uni-freiburg.de \
    --to=ukleinek@informatik.uni-freiburg.de \
    --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).