Git development
 help / color / mirror / Atom feed
From: Sean <seanlkml@sympatico.ca>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Cc: Junio C Hamano <junkio@cox.net>,
	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 09:26:44 -0500	[thread overview]
Message-ID: <BAYC1-PASMTP03FF5D34586546629C92BBAEEF0@CEZ.ICE> (raw)
In-Reply-To: <455F1595.9020009@lsrfire.ath.cx>

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

How is git-runstatus different from "git status"?  Should this command be
viewed simply as plumbing, and if so does it deserve a man page or just
textual documentation in the source?


  reply	other threads:[~2006-11-18 14:26 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 [this message]
     [not found] ` <20061118092644.a9f15669.seanlkml@sympatico.ca>
2006-11-18 14:35   ` Petr Baudis
2006-11-18 15:04     ` Rene Scharfe
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=BAYC1-PASMTP03FF5D34586546629C92BBAEEF0@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=peff@peff.net \
    --cc=rene.scharfe@lsrfire.ath.cx \
    /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