From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: update to 5.9
Date: Tue, 13 Oct 2020 00:47:00 +0200 [thread overview]
Message-ID: <20201012224700.3FGFhkTncxhN1qx9vuFqCcBzuXNO6kILSyAkYJ1PYGY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25546@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/25546#issuecomment-707382591
Comment:
As for the patches here and why pmOS does not apply them: https://fosstodon.org/@martijnbraam/105024221271723531
I think they got a point, but that obv depends on whether we actually run into the issues they don't run into..
next prev parent reply other threads:[~2020-10-12 22:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 18:43 [PR PATCH] " CameronNemo
2020-10-12 22:31 ` jcgruenhage
2020-10-12 22:46 ` jcgruenhage
2020-10-12 22:47 ` jcgruenhage [this message]
2020-10-12 23:41 ` sgn
2020-10-12 23:41 ` sgn
2020-10-12 23:45 ` jcgruenhage
2020-10-12 23:49 ` jcgruenhage
2020-10-13 1:51 ` [PR PATCH] [Updated] " CameronNemo
2020-10-13 2:06 ` CameronNemo
2020-10-13 15:02 ` jcgruenhage
2020-10-13 17:16 ` jcgruenhage
2020-10-26 3:04 ` [PR PATCH] [Updated] " CameronNemo
2020-10-26 3:06 ` CameronNemo
2020-10-27 2:36 ` CameronNemo
2020-10-27 3:51 ` jcgruenhage
2020-10-27 16:24 ` CameronNemo
2020-11-02 15:47 ` [PR PATCH] [Updated] " CameronNemo
2020-11-02 17:44 ` pinebookpro-kernel: update to 5.9.3 CameronNemo
2020-11-06 19:37 ` [PR PATCH] [Updated] " CameronNemo
2020-11-21 17:22 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 5.9.6 CameronNemo
2020-11-25 20:21 ` pinebookpro-kernel: update to 5.9.8 ericonr
2020-12-03 6:26 ` [PR PATCH] [Updated] " CameronNemo
2020-12-03 6:28 ` pinebookpro-kernel: update to 5.9.12 CameronNemo
2020-12-03 20:49 ` [PR PATCH] [Merged]: " ericonr
2020-12-22 8:20 ` Johnnynator
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=20201012224700.3FGFhkTncxhN1qx9vuFqCcBzuXNO6kILSyAkYJ1PYGY@z \
--to=jcgruenhage@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).