Standardization of messages - dot after the sentence

Standardization of messages - dot after the sentence

[sigo]

I've found really "little bug" with dots in the git output.

$ git push
Everything up-to-date

git pull
Already up-to-date.

Could all phrases contain dots? :)

Re: Standardization of messages - dot after the sentence

[Michael J Gruber]

sigo venit, vidit, dixit 05.09.2015 14:22:
> I've found really "little bug" with dots in the git output.
> 
> $ git push
> Everything up-to-date
> 
> git pull
> Already up-to-date.
> 
> Could all phrases contain dots? :)
> 

In this case, also both messages mean the same but are phrased
differently, which is suboptimal in more than one way.

It would be good to change them systematically (not just in these 2
spots) - and that would make for a perfect first foray into submitting
patches, hint hint hint :)

Michael

Re: Standardization of messages - dot after the sentence

[Junio C Hamano]

Michael J Gruber <git@drmicha.warpmail.net> writes:

> sigo venit, vidit, dixit 05.09.2015 14:22:
>> I've found really "little bug" with dots in the git output.
>> 
>> $ git push
>> Everything up-to-date
>> 
>> git pull
>> Already up-to-date.
>> 
>> Could all phrases contain dots? :)
>> 
>
> In this case, also both messages mean the same but are phrased
> differently, which is suboptimal in more than one way.

I do not particularly care between these two commands, but I think
"git pull" says the same "Already up-to-date" in two situations that
are two quite different ones.  That ambiguity bothers me a lot more.

Re: Standardization of messages - dot after the sentence

[Michael J Gruber]

Junio C Hamano venit, vidit, dixit 08.09.2015 20:16:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
> 
>> sigo venit, vidit, dixit 05.09.2015 14:22:
>>> I've found really "little bug" with dots in the git output.
>>>
>>> $ git push
>>> Everything up-to-date
>>>
>>> git pull
>>> Already up-to-date.
>>>
>>> Could all phrases contain dots? :)
>>>
>>
>> In this case, also both messages mean the same but are phrased
>> differently, which is suboptimal in more than one way.
> 
> I do not particularly care between these two commands, but I think
> "git pull" says the same "Already up-to-date" in two situations that
> are two quite different ones.  That ambiguity bothers me a lot more.

I think both are bad in the same way:

If a user sees two different messages she rightfully assumes there is a
difference. If she sees two same messages she righfully assumes there is
no difference.

Besides: l10n...

Michael