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

On Tue, Jun 30, 2009 at 01:33:05AM -0400, Jeff King wrote:
> If it is convenience you want, perhaps you would be even happier with:
>   git config status.showUntrackedFiles no

No, that doesn't help in my usecase. I want to be reminded about the
untracked files by default because I intend to clean them up later.

> [...] 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".

> So I am a little hesitant to endorse its use in "git status" for something
> unrelated (and I am hesitant to have redundant command line options, as
> well).

Yes I understand that. I'm using a wrapper script for now, but if it was any
other one-letter shortcut, I would prefer to learn that instead.

bye,
Martin

  reply	other threads:[~2009-06-30 15:15 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 [this message]
2009-06-30 15:33         ` Jeff King
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=20090630151442.GA20688@old.homeip.net \
    --to=martinxyz@gmx.ch \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).