Github messages for voidlinux
 help / color / mirror / Atom feed
From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: linux-surface 5.13.13
Date: Sat, 04 Sep 2021 04:35:32 +0200	[thread overview]
Message-ID: <20210904023532.-r8Cd2zyo9Y6lJZU8Ifapdvgkcl3azYhn_YKpyM8yec@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32823@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

New comment by CameronNemo on void-packages repository

https://github.com/void-linux/void-packages/pull/32823#issuecomment-912893693

Comment:
>The patches are a copy from the linux-surface repo (I have a shell script that always copies over the most up to date ones)

Why maintain the patches in the void-packages repo, though? There are a lot of them and nobody really knows what they do or how to rebase them if need be. Why not just download the repo and apply the patches from there?

Also FYI they don't seem to support Linux 5.13, you probably want to use 5.10 (which is an LTS kernel). https://github.com/linux-surface/linux-surface/tree/master/patches#maintained-versions

  parent reply	other threads:[~2021-09-04  2:35 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 19:02 [PR PATCH] " RononDex
2021-09-03 19:12 ` RononDex
2021-09-03 19:28 ` RononDex
2021-09-04  2:35 ` CameronNemo [this message]
2021-09-04  9:05 ` RononDex
2021-09-04  9:06 ` RononDex
2021-09-04  9:24 ` q66
2021-09-04  9:33 ` RononDex
2021-09-06  7:44 ` [PR PATCH] [Updated] " RononDex
2021-09-06  7:45 ` RononDex
2021-09-06  7:47 ` RononDex
2021-09-06 13:48 ` RononDex
2021-09-06 17:15 ` [PR REVIEW] " Chocimier
2021-09-06 17:15 ` Chocimier
2021-09-06 17:15 ` Chocimier
2021-09-06 17:15 ` Chocimier
2021-09-06 17:15 ` Chocimier
2021-09-07  8:55 ` [PR PATCH] [Updated] " RononDex
2021-09-07 10:24 ` [PR REVIEW] " RononDex
2021-09-07 10:24 ` RononDex
2021-09-07 10:25 ` RononDex
2021-09-07 13:42 ` [PR PATCH] [Updated] " RononDex
2021-09-07 13:44 ` [PR REVIEW] " RononDex
2021-09-07 15:54 ` [PR PATCH] [Updated] " RononDex
2021-09-07 15:55 ` [PR REVIEW] " RononDex
2021-09-07 17:53 ` RononDex
2021-09-07 20:00 ` RononDex
2021-09-07 22:51 ` q66
2021-09-08  9:10 ` [PR PATCH] [Updated] " RononDex
2021-09-08  9:11 ` RononDex
2021-09-08  9:48 ` [PR PATCH] [Updated] " RononDex
2021-09-08 13:23 ` RononDex
2021-09-08 14:27 ` q66
2021-09-10 20:10 ` [PR PATCH] [Updated] " RononDex
2021-09-10 20:10 ` RononDex
2021-09-10 20:10 ` RononDex
2021-09-10 21:00 ` q66
2021-09-10 22:20 ` RononDex
2021-09-10 22:21 ` RononDex
2021-09-10 22:25 ` RononDex
2021-09-10 22:25 ` q66
2021-09-10 22:37 ` q66
2021-09-10 22:40 ` RononDex
2021-09-10 23:02 ` q66
2021-09-11  7:02 ` RononDex
2021-09-11 20:21 ` Chocimier
2021-09-15 12:54 ` [PR PATCH] [Updated] " RononDex
2021-09-15 12:56 ` RononDex
2021-09-15 12:56 ` RononDex
2021-09-15 16:20 ` [PR PATCH] [Updated] " RononDex
2021-09-17 14:06 ` RononDex
2021-09-25 13:50 ` RononDex
2021-09-25 14:00 ` q66
2021-09-27 20:08 ` Chocimier
2021-09-27 21:33 ` q66
2022-06-05  2:14 ` github-actions
2022-06-19  2:15 ` [PR PATCH] [Closed]: " github-actions
2023-08-14  8:08 ` Anachron

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=20210904023532.-r8Cd2zyo9Y6lJZU8Ifapdvgkcl3azYhn_YKpyM8yec@z \
    --to=cameronnemo@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).