git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elfyn McBratney <beu@gentoo.org>
To: git mailing list <git@vger.kernel.org>
Cc: Petr Baudis <pasky@suse.cz>
Subject: [COGITO] cg-status in an empty repo spits out git-diff-index usage info
Date: Fri, 30 Sep 2005 19:18:09 +0100	[thread overview]
Message-ID: <20050930181809.GB13582@emcb.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

[Re-sending ..]

Hello Petr, git list,

A `cg-status` in an empty repo (i.e., straight after a `cg-init -I`)
spits out git-diff-index usage information, a la:

	[($) 09:03:42] beu@zippy ~/git/test
	> cg-status
	Heads:
	    >master
	    
	    usage: git-diff-index [-m] [--cached] [<common diff options>] <tree-ish> [<path>...]
	    common diff options:
	    [...]

which I'm guessing isn't expected behaviour ;)  `git status` does the
same, FWIW.  I'm having a look around to try and figure out why, and
will try to work up a patch to fix it, but in case I don't find the bug
(or feature ;), consider this a heads-up. :)

(And I've just used gitk for the first time, too, and I must say it's
one invaluable piece of software !  Kudos to it's creators :)

This is with latest cogito.git (b06f2a707963c8712f7a6bbd4b89bae758bcf92a,
though the 'bug' is also present in 0.15.1) with git 0.99.7d.

Best,
Elfyn

-- 
Elfyn McBratney
Gentoo Developer/Perl Team Lead
beu/irc.freenode.net                            http://dev.gentoo.org/~beu/
+------------O.o--------------------- http://dev.gentoo.org/~beu/pubkey.asc

PGP Key ID: 0x69DF17AD
PGP Key Fingerprint:
  DBD3 B756 ED58 B1B4 47B9  B3BD 8D41 E597 69DF 17AD

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-09-30 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 18:18 Elfyn McBratney [this message]
2005-10-01  7:17 ` [COGITO] cg-status in an empty repo spits out git-diff-index usage info Junio C Hamano
2005-10-04 13:02   ` Elfyn McBratney

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=20050930181809.GB13582@emcb.local \
    --to=beu@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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).