git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nicholas Guriev <guriev-ns@ya.ru>
Cc: Eric Sunshine <sunshine@sunshineco.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH v2] status: -i shorthand for --ignored command line option
Date: Thu, 09 Aug 2018 08:44:39 -0700	[thread overview]
Message-ID: <xmqqpnyrczo8.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180809062142.15638-1-guriev-ns@ya.ru> (Nicholas Guriev's message of "Thu, 9 Aug 2018 09:21:42 +0300")

Nicholas Guriev <guriev-ns@ya.ru> writes:

> It allows for uniformity with the --untracked-files option. Also
> the new short flag saves the number of keys to press for the
> typically git-status command.

Unlike "-u', "-i" is supported by "git commit" which shares the
underlying implementation, and that is the historical reason why we
never had "-i" shorthand, I think.  

While I do understand why sometimes "-u" is useful, especially
"-uno", to help those whose .gitignore is not managed as well as it
should be, I am not sure why a "typical git-status" invocation would
ask for "--ignored" that often to require such a short-hand.

  reply	other threads:[~2018-08-09 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180804181539.29536-1-guriev-ns@ya.ru>
2018-08-08  6:39 ` [PATCH] status: -i shorthand for --ignored command line option Nicholas Guriev
2018-08-08  7:34   ` Eric Sunshine
2018-08-09  6:21     ` [PATCH v2] " Nicholas Guriev
2018-08-09 15:44       ` Junio C Hamano [this message]
2018-08-13  5:02         ` Коля Гурьев
2018-08-13 16:46           ` 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=xmqqpnyrczo8.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=guriev-ns@ya.ru \
    --cc=sunshine@sunshineco.com \
    /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).