git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Martin Renold <martinxyz@gmx.ch>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git status -q (similar to subversion)
Date: Tue, 30 Jun 2009 11:33:48 -0400	[thread overview]
Message-ID: <20090630153347.GA3547@sigio.peff.net> (raw)
In-Reply-To: <20090630151442.GA20688@old.homeip.net>

On Tue, Jun 30, 2009 at 05:14:42PM +0200, Martin Renold wrote:

> > [...] but we have to deal with the fact that "git status" is really a
> > dry-run version of "git commit", which already has a "-q" option
> 
> Good point. However I think those commands are similar only from an
> implementation point of view.  As an user I think of them as being quite
> different.  I would not be surprised about different meaning of options -
> certainly less than about "git commit -a" vs "git add -u".

The main difference that trips people, I think, is that they expect "git
status <file>" to restrict status to a subset of the tree. But it is
about "what would happen if I did 'git commit <file>'", which is quite
different.

There has been much discussion about an alternate command that would be
more like "svn status", and even some partial implementations. But it
needs somebody who really cares about the feature to step up and
complete it.

-Peff

  reply	other threads:[~2009-06-30 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27 20:57 [PATCH] git status -q (similar to subversion) Unknown
2009-06-28 18:52 ` Jeff King
2009-06-28 21:01   ` Martin Renold
2009-06-30  5:33     ` Jeff King
2009-06-30 15:14       ` Martin Renold
2009-06-30 15:33         ` Jeff King [this message]
2009-07-01  8:37           ` Paolo Bonzini
2009-06-28 22:44 ` David Aguilar
2009-06-29 19:39   ` Unknown
2009-06-30  5:33     ` Jeff King
2009-06-30 16:56       ` Unknown

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=20090630153347.GA3547@sigio.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=martinxyz@gmx.ch \
    /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).