From: Max Kirillov <max@max630.net>
To: Alex Kuleshov <kuleshovmail@gmail.com>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Paul Mackerras <paulus@samba.org>, Git <git@vger.kernel.org>
Subject: Re: [PATCH 1/1] gitk: po/ru.po russian translation typo fixed
Date: Tue, 18 Nov 2014 07:23:03 +0200 [thread overview]
Message-ID: <20141118052303.GB4808@wheezy.local> (raw)
In-Reply-To: <87d28mb6jb.fsf@gmail.com>
On Mon, Nov 17, 2014 at 01:59:28PM +0600, Alex Kuleshov wrote:
>
> Hello Max and Paul,
>
> thank you for your feedback, so what's must be my next workflow? Resend
> patch with "Reviewed-By:..." or somethine else?
To be honest I don't know. The only time I had such an
answer maintainer put the flag himself at applying patch.
--
Max
next prev parent reply other threads:[~2014-11-18 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 11:05 [PATCH 1/1] gitk: po/ru.po russian translation typo fixed 0xAX
2014-11-14 21:16 ` Max Kirillov
[not found] ` <CALxABCbZCy_DY-JkO+PuS9d6VUnaBSb68aDFyv9usR5gKjicvA@mail.gmail.com>
2014-11-17 7:59 ` Alex Kuleshov
2014-11-18 5:23 ` Max Kirillov [this message]
2015-03-22 3:40 ` Paul Mackerras
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=20141118052303.GB4808@wheezy.local \
--to=max@max630.net \
--cc=git@vger.kernel.org \
--cc=kuleshovmail@gmail.com \
--cc=paulus@samba.org \
--cc=raa.lkml@gmail.com \
/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).