From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Bartosz Golaszewski" <brgl@bgdev.pl>,
"Kent Gibson" <warthog618@gmail.com>
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 17:18:12 +0100 [thread overview]
Message-ID: <CYCV3N24HKCG.1W9TO82K8QOPD@ablu-work> (raw)
In-Reply-To: <CAMRc=Mc0dLkjnOrM2QdVkOhnXccHv6hFu0WPEuL31hGLKkJpbw@mail.gmail.com>
On Fri Jan 12, 2024 at 5:07 PM CET, Bartosz Golaszewski wrote:
> On Fri, Jan 12, 2024 at 4:40 PM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > On Fri, Jan 12, 2024 at 11:25:02PM +0800, Kent Gibson wrote:
> > > 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?
> > >
> >
> > The Releases section could use updating - it lists the latest as v0.3
> > from June 2017!
> >
>
> I don't want to do releases on github. The right place to fetch the
> releases from is kernel.org[1] (I should add this link to README too)
> and I don't want to duplicate release tarballs. I'm pretty sure people
> would start fetching releases from github for distros etc.
You might want to delete the old tags from the github remote in that
case. I think it might be a bit confusing to see v0.3 as "most recent"
release otherwise.
- Erik
next prev parent reply other threads:[~2024-01-12 16:18 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
2024-01-12 15:40 ` Kent Gibson
2024-01-12 16:07 ` Bartosz Golaszewski
2024-01-12 16:18 ` Erik Schilling [this message]
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=CYCV3N24HKCG.1W9TO82K8QOPD@ablu-work \
--to=erik.schilling@linaro.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=phil@gadgetoid.com \
--cc=warthog618@gmail.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.