From: Junio C Hamano <gitster@pobox•com>
To: Jacob Keller <jacob.keller@gmail•com>
Cc: Michael J Gruber <git@grubix•eu>, Git mailing list <git@vger•kernel.org>
Subject: Re: [PATCH] status: show in-progress info for short status
Date: Wed, 12 Apr 2017 23:09:32 -0700 [thread overview]
Message-ID: <xmqqmvbkq1nn.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CA+P7+xr37owZbCnwVKh0y_vUny9_pP380Y8sFA+7A-hv0Oc6AA@mail.gmail.com> (Jacob Keller's message of "Fri, 7 Apr 2017 09:18:01 -0700")
Jacob Keller <jacob.keller@gmail•com> writes:
> Personally, I would want this to become the default and not have a new
> option to trigger it. I think we could also extend the porcelain
> format to include this information as well, but I'm not too familiar
> with how the v2 format extends or not.
I think the general rule of thumb for --porcelain is that we can
freely introduce new record types without version bump, and expect
the reading scripts to ignore unrecognised records (we may need to
describe this a bit more strongly in our document, though), while
changes to the format of existing records must require a command
line option that cannot be turned on by default with configuration
(or a version bump, if you want to change the output format by
default).
I am getting the impression that this "we are doing X" is a new and
discinct record type that existing readers can safely ignore? If
that is the case, it may be better to add it without making it
optional.
next prev parent reply other threads:[~2017-04-13 6:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 13:59 [PATCH] status: show in-progress info for short status Michael J Gruber
2017-03-31 18:14 ` Junio C Hamano
2017-04-07 14:14 ` Michael J Gruber
2017-04-07 16:18 ` Jacob Keller
2017-04-13 6:09 ` Junio C Hamano [this message]
2017-04-13 7:20 ` Jacob Keller
2017-05-11 2:45 ` Junio C Hamano
2017-04-13 7:21 ` Jacob Keller
2017-04-01 13:51 ` brian m. carlson
2017-04-06 14:33 ` SZEDER Gábor
2017-04-07 14:05 ` Michael J Gruber
2017-04-13 10:43 ` SZEDER Gábor
2017-04-17 7:06 ` 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=xmqqmvbkq1nn.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@grubix$(echo .)eu \
--cc=git@vger$(echo .)kernel.org \
--cc=jacob.keller@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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