Re: [PATCH v2 1/2] git-prompt: make __git_eread intended use explicit
- From
Robert Abel <rabel@robertabel.eu>
- Date
- Dec 5, 2017, 07:01 UTC
- Message-ID
- <818f414b-76ab-6e1d-0c5c-7f9959223e64@robertabel.eu>
- In-Reply-To
- <xmqqd13ukohs.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On 05 Dec 2017 01:27, Junio C Hamano wrote:
> I know all of the above, but I think you misunderstood the point I > wanted to raise, so let me try again. The thing is, none of what > you just wrote changes the fact that lack of callers that want to do > "multi-line" is IRRELEVANT.
I disagree. The commit comment is meant to give context to the introduced changes. One change is the additional comment for __git_eread, which now clearly states that only a single line is read.
I'm well aware that I'm not breaking reading multiple lines, because that never worked in the first place. Thus, it was never the indented use for __git_eread as I see it. I explicitly want to include that information in my commit message to pay it forward to the next person working on the prompt.
Regards,
Robert