From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <tr@thomasrast.ch>
Cc: git@vger.kernel.org, a.huemer@commend.com,
"Michael S. Tsirkin" <mst@kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [RFC PATCH] Revamp git-cherry(1)
Date: Thu, 21 Nov 2013 14:04:36 -0800 [thread overview]
Message-ID: <xmqqwqk12yyz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87pppt31v9.fsf@thomasrast.ch> (Thomas Rast's message of "Thu, 21 Nov 2013 22:02:02 +0100")
Thomas Rast <tr@thomasrast.ch> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>>> OPTIONS
>>> -------
>>> -v::
>>> - Verbose.
>>> + Verbose. Currently shows the commit subjects next to their
>>> + SHA1.
>>
>> Whenever I see "Currently", it makes me wonder "why does it need to
>> say that? Is there a plan to change it soon, and if so where is the
>> plan described?".
>
> I wanted to avoid documenting exactly what it does, so that in the
> future it could do more than that. Is that overly paranoid?
I would have to say so. After all, the documentation is supposed to
describe the current state of affairs, and we would update it when
"the current state" changes. In places, we may express our plan to
forewarn readers of planned upcoming changes, but still...
next prev parent reply other threads:[~2013-11-21 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 11:30 [RFC PATCH] Revamp git-cherry(1) Thomas Rast
2013-11-21 11:54 ` Jeff King
2013-11-21 20:58 ` Thomas Rast
2013-11-21 19:26 ` Junio C Hamano
2013-11-21 21:02 ` Thomas Rast
2013-11-21 22:04 ` Junio C Hamano [this message]
2013-11-22 16:29 ` [PATCH v2] " Thomas Rast
2013-11-22 19:25 ` Junio C Hamano
2013-11-22 19:37 ` Thomas Rast
2013-11-22 19:39 ` 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=xmqqwqk12yyz.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=a.huemer@commend.com \
--cc=git@vger.kernel.org \
--cc=mst@kernel.org \
--cc=peff@peff.net \
--cc=tr@thomasrast.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.