From: Junio C Hamano <gitster@pobox.com>
To: "Eric N. Vander Weele" <ericvw@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] status: teach "status --short" to respect "--show-stash"
Date: Thu, 07 Nov 2019 20:09:34 +0900 [thread overview]
Message-ID: <xmqqimnwoscx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191107103141.GA87008@helium> (Eric N. Vander Weele's message of "Thu, 7 Nov 2019 18:31:41 +0800")
"Eric N. Vander Weele" <ericvw@gmail.com> writes:
>> Isn't this information available to scripts that want to read from
>> porcelain v2 output format (which is meant to be extensible by
>> allowing easy-to-parse optional headers, which this stash thing
>> exactly is).
>
> It is not available in Porcelain Format v2... yet :).
>
>
> I'm happy making '--show-stash' congruent with '--branch' in v1', which
> is would be in line with documented behavior, displaying something in
> v2 only, or both. Let me know how you would like to proceed and I'll
> rework the patch accordingly.
Quite honestly, you do not want to ask _me_. If you left it to
me, I may say that, among the possible next step you listed, the
best one is to do nothing, as I do not want to see the stash info in
the "status --short" output ;-)
It probably is the safest to make it available first only in v2
format. I do not know if that makes its utility too limited for the
purpose of the application you have in mind.
next prev parent reply other threads:[~2019-11-07 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 10:03 [PATCH] status: teach "status --short" to respect "--show-stash" Eric N. Vander Weele
2019-11-06 2:33 ` Junio C Hamano
2019-11-07 10:31 ` Eric N. Vander Weele
2019-11-07 11:09 ` Junio C Hamano [this message]
2019-11-08 3:24 ` Eric N. Vander Weele
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimnwoscx.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=ericvw@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).