Re: [PATCH] Make git status usage say git status instead of git commit

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Make git status usage say git status instead of git commit

From: Florian Weimer <hidden>
Date: 2016-06-15 22:43:55

* David Kastrup:
Deprecating the dash form will probably mean that we need to think up
(and document) a rationale for

  man git-commit

I actually have typed something like

  man git commit

a number of times already with obvious results.  Finger memory.
It's also a bit strange to have a git-commit(1) manpage when there is no
git-commit on the path.

Re: [PATCH] Make git status usage say git status instead of git commit

From: Eyvind Bernhardsen <hidden>
Date: 2016-06-15 22:43:55

On 3. des. 2007, at 11.15, Florian Weimer wrote:
* David Kastrup:
quoted
Deprecating the dash form will probably mean that we need to think up
(and document) a rationale for

  man git-commit

I actually have typed something like

  man git commit

a number of times already with obvious results.  Finger memory.
It's also a bit strange to have a git-commit(1) manpage when there  
is no
git-commit on the path.
No stranger than having a perlfunc(1) manpage.  bash-builtins is in  
section 7, maybe git-* should be moved there?  Of course, then git  
wouldn't have any manpages in section 1 at all.

Eyvind
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help