[aur-requests] [PRQ#11833] Deletion Request for linux-amd-staging-git
yurikoles [1] filed a deletion request for linux-amd-staging-git [2]:
Not updating upstream.
[1] https://aur.archlinux.org/account/yurikoles/ [2] https://aur.archlinux.org/pkgbase/linux-amd-staging-git/
On 06/16/2018 10:29 PM, notify--- via aur-requests wrote:
yurikoles [1] filed a deletion request for linux-amd-staging-git [2]:
Not updating upstream.
[1] https://aur.archlinux.org/account/yurikoles/ [2] https://aur.archlinux.org/pkgbase/linux-amd-staging-git/
Is this the same as https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
Because there's definitely other branches besides the one this PKGBUILD currently uses, which do get updates.
Yes, it's mostly the same. Thank you for mentioning other branches. I hope to create different packages for this branches. Now I just manually switch the branch to most recent one, e.g. 4.19-wip -> 4.19 -> drm-next in second package.
Now I think to create linux-amd-staging-wip, that points to $ver-wip and point this package to $ver. And point second package to drm-next. There is also drm-next from drm subsystem maintainer, which accumulates patches for all drivers in one repo.
Because of that I think that maybe it will be better to create an interective AIO package to make it easy to maintain?
ср, 11 лип. 2018, 06:07 користувач Eli Schwartz eschwartz@archlinux.org пише:
On 06/16/2018 10:29 PM, notify--- via aur-requests wrote:
yurikoles [1] filed a deletion request for linux-amd-staging-git [2]:
Not updating upstream.
[1] https://aur.archlinux.org/account/yurikoles/ [2] https://aur.archlinux.org/pkgbase/linux-amd-staging-git/
Is this the same as https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
Because there's definitely other branches besides the one this PKGBUILD currently uses, which do get updates.
-- Eli Schwartz Bug Wrangler and Trusted User
Is it possible to read and save info about desired branch/repo from some config, e.g. ~/.config/linux-amd-git-branch?
ср, 11 лип. 2018, 13:55 користувач Yurii Kolesnykov yurikoles@gmail.com пише:
Yes, it's mostly the same. Thank you for mentioning other branches. I hope to create different packages for this branches. Now I just manually switch the branch to most recent one, e.g. 4.19-wip -> 4.19 -> drm-next in second package.
Now I think to create linux-amd-staging-wip, that points to $ver-wip and point this package to $ver. And point second package to drm-next. There is also drm-next from drm subsystem maintainer, which accumulates patches for all drivers in one repo.
Because of that I think that maybe it will be better to create an interective AIO package to make it easy to maintain?
ср, 11 лип. 2018, 06:07 користувач Eli Schwartz eschwartz@archlinux.org пише:
On 06/16/2018 10:29 PM, notify--- via aur-requests wrote:
yurikoles [1] filed a deletion request for linux-amd-staging-git [2]:
Not updating upstream.
[1] https://aur.archlinux.org/account/yurikoles/ [2] https://aur.archlinux.org/pkgbase/linux-amd-staging-git/
Is this the same as https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
Because there's definitely other branches besides the one this PKGBUILD currently uses, which do get updates.
-- Eli Schwartz Bug Wrangler and Trusted User
Request #11833 has been accepted by Alad [1].
participants (3)
-
Eli Schwartz
-
notify＠aur.archlinux.org
-
Yurii Kolesnykov