Re: [PATCH v2] sequencer.c: fix and unify error messages in rearrange_squash()
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 16, 2017, 11:32 UTC
- Message-ID
- <alpine.DEB.2.21.1.1710161331290.40514@virtualbox>
- In-Reply-To
- <xmqqfuajuae8.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Mon, 16 Oct 2017, Junio C Hamano wrote:
Show 11 quoted lines
> Ralf Thielow <ralf.thielow@gmail.com> writes: > > > When the write opertion fails, we write that we could > > not read. Change the error message to match the operation > > and remove the full stop at the end. > > > > When ftruncate() fails, we write that we couldn't finish > > the operation on the todo file. It is more accurate to write > > that we couldn't truncate as we do in other calls of ftruncate(). > > Wouldn't it be more accurate to say we couldn't ftruncate, though?
This is an end-user facing error message, right? Should we not let users who are happily oblivious of POSIX nomenclature remain happily oblivious?
In other words, I would be finer with "truncate" than with "ftruncate... wait, huh? Is that even English?"
Ciao, Dscho