From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [RFC] CONTRIBUTING.md
Date: Mon, 21 Aug 2017 11:35:04 +0200 [thread overview]
Message-ID: <20170821093504.GA8387@yssyq.radix50.net> (raw)
In-Reply-To: <20170821105827.26a190f4@md1em3qc>
On Mon, Aug 21, 2017 at 10:58:27AM +0200, Henning Schild wrote:
> > I think it wasn't on the list, was it?
>
> No, it just showed up in git. That is why i did not take the RFC too
> serious. But according to its content that should be the last commit
> that took the fast-lane.
It wasn't on the list. It is not about "fast-lane". It is intended to show the
state of the things till that moment. Now, more people are contributing, and we
might possibly need to change something. The goal is that any such changes are
visible also in the git history and not only in the ML archives. So, comments
are welcome.
As promised, manifest and coding style docs are on my TODO; I'm planning to do
that in the same way, with the same goal.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2017-08-21 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 10:07 Baurzhan Ismagulov
2017-08-19 13:55 ` Jan Kiszka
2017-08-21 8:58 ` Henning Schild
2017-08-21 9:35 ` Baurzhan Ismagulov [this message]
2017-08-21 23:47 ` Baurzhan Ismagulov
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=20170821093504.GA8387@yssyq.radix50.net \
--to=ibr@radix50.net \
--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