All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Phil Howard <phil@gadgetoid.com>,
	linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH] README: add info about the github page
Date: Fri, 12 Jan 2024 23:25:02 +0800	[thread overview]
Message-ID: <20240112152502.GA92656@rigel> (raw)
In-Reply-To: <20240112150546.13891-1-brgl@bgdev.pl>

On Fri, Jan 12, 2024 at 04:05:46PM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> The github page over at https://github.com/brgl/libgpiod has been reopened
> for bug reports and discussions. Add a link and a mention to the README
> file.
>

No problem with the patch, but the github page itself seems to have
Issues and Discussions disabled.  And the Wiki might be useful too?

Reviewed-by: Kent Gibson <warthog618@gmail.com>

> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
>  README | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/README b/README
> index 69128dc..41237f4 100644
> --- a/README
> +++ b/README
> @@ -294,9 +294,14 @@ Those also provide examples of the expected formatting.
>  Allow some time for your e-mail to propagate to the list before retrying,
>  particularly if there are no e-mails in the list more recent than yours.
>
> +There is a libgpiod github page[7] available for reporting bugs and general
> +discussions and although PRs can be submitted and discussed, upstreambound
> +patches need to go through the mailing list nevertheless.
> +
>  [1] https://github.com/kward/shunit2
>  [2] http://vger.kernel.org/vger-lists.html#linux-gpio
>  [3] https://docs.kernel.org/process/email-clients.html
>  [4] https://docs.kernel.org/process/coding-style.html
>  [5] https://docs.kernel.org/process/submitting-patches.html
>  [6] https://lore.kernel.org/linux-gpio/
> +[7] https://github.com/brgl/libgpiod
> --
> 2.40.1
>

  reply	other threads:[~2024-01-12 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:05 [libgpiod][PATCH] README: add info about the github page Bartosz Golaszewski
2024-01-12 15:25 ` Kent Gibson [this message]
2024-01-12 15:40   ` Kent Gibson
2024-01-12 16:07     ` Bartosz Golaszewski
2024-01-12 16:18       ` Erik Schilling
2024-01-15  9:37         ` Bartosz Golaszewski
2024-01-13  2:25       ` Kent Gibson
2024-01-12 15:26 ` Erik Schilling
2024-01-12 16:05   ` Bartosz Golaszewski
2024-01-12 16:13     ` Erik Schilling
2024-01-13  1:57       ` Kent Gibson

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=20240112152502.GA92656@rigel \
    --to=warthog618@gmail.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=phil@gadgetoid.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.