From: Eiji Tanioka <tanioka404@gmail.com>
To: Vasili Pupkin <diggest@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH] Update Simplified Chinese translation
Date: Sun, 1 Mar 2020 15:53:57 +0900 [thread overview]
Message-ID: <CAA2ss9Edo9OyoJTHq0H9-AvG2ghGb60L8Z4jKoEWP5GtdF26wg@mail.gmail.com> (raw)
In-Reply-To: <5428f486-49cd-0321-de5b-9ef6ca3e8dad@gmail.com>
Why don't you use `git format-patch`, `git send-email` and send to ML?
In "Source Code Repositories and Official Projects" page (
https://www.wireguard.com/repositories/ ), wireguard-android requires
`git send-email` and send to ML.
And Samuel Holland is not the only committer of wireguard-android,
other committer in ML can review your patch and apply source tree.
If you use required format, your patch will accept more quickly, I think.
Bes Regards,
Eiji Tanioka
2020年2月29日(土) 21:55 Vasili Pupkin <diggest@gmail.com>:
>
> On 29.02.2020 11:35, Eiji Tanioka wrote:
> > Hi Vasili!
> >
> > Did you send patch to ML?
> > If so, I think that your patch is in the moderation queue. I had met
> > same situation when sending my patch because of body size (over 40
> > KB).
> >
> > I think it's okay if you wait.
>
> No. I've just sent it to Samuel Holland to his email only. It's not a
> git patch, just a simple diff patch to the russian language strings,
> without the authorship.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-03-01 6:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 11:12 srb12345
2020-02-25 0:56 ` Samuel Holland
2020-02-25 8:13 ` Eiji Tanioka
2020-02-26 2:56 ` Samuel Holland
2020-02-26 3:10 ` Eiji Tanioka
2020-02-26 3:44 ` Vasili Pupkin
2020-02-26 3:59 ` Samuel Holland
2020-02-29 7:00 ` Vasili Pupkin
2020-02-29 8:35 ` Eiji Tanioka
2020-02-29 8:54 ` Jason A. Donenfeld
[not found] ` <5428f486-49cd-0321-de5b-9ef6ca3e8dad@gmail.com>
2020-03-01 6:53 ` Eiji Tanioka [this message]
2020-03-01 7:00 ` Jason A. Donenfeld
2020-02-26 3:21 =?gb18030?B?TWF0c3VyaQ==?=
2020-03-12 11:40 srb12345
2020-03-12 11:47 ` Harsh Shandilya
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=CAA2ss9Edo9OyoJTHq0H9-AvG2ghGb60L8Z4jKoEWP5GtdF26wg@mail.gmail.com \
--to=tanioka404@gmail.com \
--cc=diggest@gmail.com \
--cc=wireguard@lists.zx2c4.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).