Extract files one at a time from all-cabal-hashes #32772
Conversation
|
@shlevy Didn't know if I should update |
|
Hmmm a PR to release-17.03? 17.03 hasn't been supported for 4 months now. |
|
Just acting on this request: #31333 (comment) |
|
@grahamc Is it a problem to merge things back so long as users know they have to do the work themselves to keep it secure and up-to-date? |
|
Hmm not sure. Has any attempt been made to ensure the requester knows 17.03
is no longer supported?
…On Sun, Dec 17, 2017 at 8:45 PM Shea Levy ***@***.***> wrote:
@grahamc <https://github.com/grahamc> Is it a problem to merge things
back so long as users know they have to do the work themselves to keep it
secure and up-to-date?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#32772 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAErrH8Pug4oFFUSstN06AxGA3tPm_8vks5tBcPXgaJpZM4REw14>
.
|
|
@grahamc I told them when I worked there 😉 |
|
Will this be merged? |
|
@mightybyte Do you need this? Could you share a bit on why you'd rather not switch to 17.09? |
|
@ElvishJerricco Is Takt aware that 17.03 is unmaintained and may miss critical security updates if they don't support them themselves? If so then I think we can merge your changes. |
|
@mightybyte thoughts? |
|
Yes, this would be very useful for us. Switching to 17.09 has not proven to be trivial. Also, less than a year of official support for major releases is not great when it comes to supporting mission-critical codebases. |
Motivation for this change
Things done
build-use-sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)