From: garciagj <garciagj@ensibm.imag.fr>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Junio C Hamano <gitster@pobox.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Jorge Juan Garcia Garcia
<Jorge-Juan.Garcia-Garcia@ensimag.imag.fr>, <git@vger.kernel.org>,
Mathieu Lienard--Mayor <Mathieu.Lienard--Mayor@ensimag.imag.fr>
Subject: Re: [PATCH 1/2] status: introduce status.short to enable --short by default
Date: Mon, 10 Jun 2013 10:02:39 +0200 [thread overview]
Message-ID: <9646ae430a3789ab2a7a968b337f0a8c@ensibm.imag.fr> (raw)
In-Reply-To: <vpqbo7frspc.fsf@anie.imag.fr>
El 2013-06-09 21:26, Matthieu Moy escribió:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Ramkumar Ramachandra <artagnon@gmail.com> writes:
>>
>>> Jorge Juan Garcia Garcia wrote:
>>>> Some people always run 'git status -s'.
>>>> The configuration variable status.short allows to set it by
>>>> default.
>>>
>>> Good feature.
>>
>> Is there a corresponding command line override added to help people
>> who need to defeat such a configured-in default?
>
> Yes: "git status --no-short".
>
> Perhaps the doc for status.short should explicitely mention that
> --no-short takes precedence over it.
Yes, I will include that in the Documentation.
next prev parent reply other threads:[~2013-06-10 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 9:28 [PATCH 1/2] status: introduce status.short to enable --short by default Jorge Juan Garcia Garcia
2013-06-08 9:28 ` [PATCH 2/2] status: introduce status.branch to enable --branch " Jorge Juan Garcia Garcia
2013-06-08 15:25 ` [PATCH 1/2] status: introduce status.short to enable --short " Ramkumar Ramachandra
2013-06-09 18:54 ` Junio C Hamano
2013-06-09 19:26 ` Matthieu Moy
2013-06-10 8:02 ` garciagj [this message]
2013-06-10 8:01 ` garciagj
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=9646ae430a3789ab2a7a968b337f0a8c@ensibm.imag.fr \
--to=garciagj@ensibm.imag.fr \
--cc=Jorge-Juan.Garcia-Garcia@ensimag.imag.fr \
--cc=Mathieu.Lienard--Mayor@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).