Git development
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>
Cc: Sean <seanlkml@sympatico.ca>,
	Git Mailing List <git@vger.kernel.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH] Document git-runstatus
Date: Sat, 18 Nov 2006 16:04:43 +0100	[thread overview]
Message-ID: <455F210B.8000107@lsrfire.ath.cx> (raw)
In-Reply-To: <20061118143511.GM7201@pasky.or.cz>

Petr Baudis schrieb:
> On Sat, Nov 18, 2006 at 03:26:44PM CET, Sean wrote:
>> On Sat, 18 Nov 2006 15:15:49 +0100
>> Rene Scharfe <rene.scharfe@lsrfire.ath.cx> wrote:
>>
>>> I copied most of the text from git-status.txt.
>> [...]	
>>> +git-runstatus - Show working tree status
> 
> Don't forget to add it to the list of commands.

Good catch, thanks.  An incremental patch follows below.

>> How is git-runstatus different from "git status"?
> 
> I have the same question.

git-status is a wrapper around git-runstatus that takes the same
options as git-commit.  It could have been named 'git-commit --dry-run'.

>> Should this command be viewed simply as plumbing, and if so does it
>> deserve a man page or just textual documentation in the source?
> 
> All commands deserve a man page.

Exactly.  Even plumbers read manuals ;-).  Well, me at least.

René


diff --git a/Documentation/git.txt b/Documentation/git.txt
index 52bc05a..63b1746 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -424,6 +424,9 @@ gitlink:git-pack-redundant[1]::
 gitlink:git-rev-list[1]::
 	Lists commit objects in reverse chronological order.
 
+gitlink:git-runstatus[1]::
+	Show working tree status.
+
 gitlink:git-show-index[1]::
 	Displays contents of a pack idx file.

  reply	other threads:[~2006-11-18 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 14:15 [PATCH] Document git-runstatus Rene Scharfe
2006-11-18 14:26 ` Sean
     [not found] ` <20061118092644.a9f15669.seanlkml@sympatico.ca>
2006-11-18 14:35   ` Petr Baudis
2006-11-18 15:04     ` Rene Scharfe [this message]
2006-11-18 16:04       ` Sean
2006-11-18 18:20         ` A Large Angry SCM
2006-11-18 18:49           ` Sean
     [not found]             ` <455F60EA.2080009@gmail.com>
2006-11-18 20:04               ` Sean
     [not found]               ` <20061118150431.81076072.seanlkml@sympatico.ca>
2006-11-19 18:13                 ` Petr Baudis
2006-11-20  7:15                   ` Joshua N Pritikin
2006-11-20  8:11                     ` Jakub Narebski
2006-11-18 18:49         ` Junio C Hamano

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=455F210B.8000107@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    --cc=peff@peff.net \
    --cc=seanlkml@sympatico.ca \
    /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