Your message dated Sat, 2 Jan 2010 01:07:27 -0600
with message-id <[email protected]>
and subject line Re: Bug#462557: git-core: git <command> -h shouldn't depend on
being inside a repository
has caused the Debian Bug report #462557,
regarding Please implement "git <command> -h" option to print short usage
message
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
462557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462557
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-core
Version: 1:1.5.3.8-1
Severity: minor
Hi!
I really wonder why "git <command> -h" depends on being inside a
repository. I noticed it with "git diff -h" (add, branch does that, too):
#v+
~/git> git tag -h
usage: git-tag [-n [<num>]] -l [<pattern>] | [-a | -s | -u <key-id>] [-f | -d |
-v] [-m <msg> | -F <file>] <tagname> [<head>]
~/git> cd
~> git tag -h
fatal: Not a git repository
~>
#v-
Though, it seems to be inconsistent in that anyway: "git config -h"
doesn't write anything, "git bisect -h" does give long help instead of
just synopsis, "git gui -h" tries to start, "git diff -h" even opens the
pager but writes to stdout "error: invalid option: -h" - all together
pretty inconsistent and confusing ...
Would be nice to get that fixed, I really want to see just the short
usage message, git help <command> works as expected independent on where
it is called from.
So long,
Rhonda
--- End Message ---
--- Begin Message ---
Version: 1:1.6.6~rc0-1
Teemu Likonen wrote:
> retitle 462557 Please implement "git <command> -h" option to print short
> usage message
> severity 462557 wishlist
> thanks
>
>
> As the -h option does not even exist for many Git commands, I retitled
> this bug. If the option gets added then it might be good idea to make it
> work consistently and outside a repository.
Both bugs should be fixed by commit v1.6.6-rc0~34 (Merge branch
'jn/help-everywhere', 2009-11-20). Thanks.
--- End Message ---
