From: Phillip Wood <phillip.wood@talktalk.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] rebase -i: Add missing newline to end of message
Date: Fri, 19 May 2017 11:13:54 +0100 [thread overview]
Message-ID: <406d017b-b138-72db-d5ad-14ccf5d1f3d4@talktalk.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705182321030.3610@virtualbox>
On 18/05/17 22:21, Johannes Schindelin wrote:
> Hi Phillip,
>
> On Thu, 18 May 2017, Phillip Wood wrote:
>
>> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>>
>> The message that's printed when auto-stashed changes are successfully
>> restored was missing '\n' at the end.
>> ---
>
> Please add your Signed-off-by:, and my Acked-by:
Will do (I forgot to add --signoff to git commit). Do I need to resend
the other patches with your Acked-by: or will that happen when Junio
applies them?
I was thinking about this last night and wonder if it would be better to do
- printf(_("Applied autostash."));
+ printf("%s\n", _("Applied autostash."));
rather than
- printf(_("Applied autostash."));
+ printf(_("Applied autostash.\n"));
as it would avoid changing the translated string and also mean that the
newline couldn't be accidentally removed any typos in the translation.
Best Wishes
Phillip
next prev parent reply other threads:[~2017-05-19 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 13:41 [PATCH] rebase -i: Add missing newline to end of message Phillip Wood
2017-05-18 13:48 ` Ævar Arnfjörð Bjarmason
2017-05-18 14:53 ` Phillip Wood
2017-05-18 21:21 ` Johannes Schindelin
2017-05-19 10:13 ` Phillip Wood [this message]
2017-05-19 11:24 ` Ævar Arnfjörð Bjarmason
2017-05-19 14:35 ` Phillip Wood
2017-05-19 14:32 ` [PATCH v2] " phillip.wood
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=406d017b-b138-72db-d5ad-14ccf5d1f3d4@talktalk.net \
--to=phillip.wood@talktalk.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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