From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
Alexander Smirnov <asmirnov@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] doc: Add maintainer process
Date: Tue, 29 Aug 2017 11:52:34 +0200 [thread overview]
Message-ID: <a3a79b7f-e81e-c6aa-c43f-db476e04cae3@siemens.com> (raw)
In-Reply-To: <20170829105153.1ce179a2@md1em3qc>
On 2017-08-29 10:51, [ext] Henning Schild wrote:
> Am Mon, 28 Aug 2017 10:02:54 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>
>> This patch adds basic maintainer process description, that has been
>> used so far since the project start.
>>
>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>> ---
>> doc/maintainer.md | 47
>> +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47
>> insertions(+) create mode 100644 doc/maintainer.md
>>
>> diff --git a/doc/maintainer.md b/doc/maintainer.md
>> new file mode 100644
>> index 0000000..ddaf39b
>> --- /dev/null
>> +++ b/doc/maintainer.md
>> @@ -0,0 +1,47 @@
>> +# Introduction
>> +
>> +Isar maintainer is the person who keeps project development in
> The Isar mainteiner
maintainer
> who keeps the project dev
>
>> compliance +with contributing process definition. The purpose of this
> with the contributing
>
>> document is to +describe the maintainer process in Isar project.
>
> in the Isar project.
>
> Two sentences and 4 missing articles. I will read the rest in v2.
None of us is a native English speaker, and we are all influenced by our
mother tongue when making mistakes. Let's help each other sorting them out.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-08-29 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 7:02 [PATCH] Maintainer process Alexander Smirnov
2017-08-28 7:02 ` [PATCH] doc: Add maintainer process Alexander Smirnov
2017-08-29 8:51 ` Henning Schild
2017-08-29 9:52 ` Jan Kiszka [this message]
2017-08-29 15:54 ` Henning Schild
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=a3a79b7f-e81e-c6aa-c43f-db476e04cae3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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