From: Michael J Gruber <git@drmicha.warpmail.net>
To: sigo <spam@sigo.pl>, git@vger.kernel.org
Subject: Re: Standardization of messages - dot after the sentence
Date: Mon, 7 Sep 2015 09:14:59 +0200 [thread overview]
Message-ID: <55ED3973.2020304@drmicha.warpmail.net> (raw)
In-Reply-To: <CALx9kCVwpOvBfTxBi8gn7MBajEbuMLGP_HAJ0TW3XGzmUE0=QA@mail.gmail.com>
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
next prev parent reply other threads:[~2015-09-07 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 12:22 Standardization of messages - dot after the sentence sigo
2015-09-07 7:14 ` Michael J Gruber [this message]
2015-09-08 18:16 ` Junio C Hamano
2015-09-09 7:41 ` Michael J Gruber
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=55ED3973.2020304@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=spam@sigo.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).