From: Kent Gibson <warthog618@gmail.com>
To: linux-gpio@vger.kernel.org, brgl@bgdev.pl
Subject: Re: [PATCH] README: provide more info in Contributing
Date: Sat, 20 May 2023 11:11:28 +0800 [thread overview]
Message-ID: <ZGg6YP/4a2IuGfqE@sol> (raw)
In-Reply-To: <20230520021509.12135-1-warthog618@gmail.com>
On Sat, May 20, 2023 at 10:15:09AM +0800, Kent Gibson wrote:
> Add more detail to Contributing to make it easier for new users to
> contribute.
>
> Signed-off-by: Kent Gibson <warthog618@gmail.com>
Bah, ironically forgot the [libgpiod] prefix.
Sorry for the noise. Will resubmit.
Cheers,
Kent.
prev parent reply other threads:[~2023-05-20 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 2:15 [PATCH] README: provide more info in Contributing Kent Gibson
2023-05-20 3:11 ` Kent Gibson [this message]
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=ZGg6YP/4a2IuGfqE@sol \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
/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