Gee, thanks so much for acknowledging my release-outpaths-parallel.nix 5x faster eval checks. It would have been a real bummer if you just copied it and passed it off as your own work.
Oh wait, that’s what happened.
Gee, thanks so much for acknowledging my release-outpaths-parallel.nix 5x faster eval checks. It would have been a real bummer if you just copied it and passed it off as your own work.
Oh wait, that’s what happened.
From the git commit headers:
commit 4874faf540622570ffc1ab545c05080ebe54b974 (HEAD -> infinisil)
Author: Silvan Mosberger <silvan.mosberger@tweag.io>
Date: Thu Nov 14 23:14:20 2024 +0100
[WIP] Parallel GH actions workflow for Nixpkgs eval
Partly taken from https://github.com/NixOS/nixpkgs/pull/352808 and https://github.com/NixOS/nixpkgs/pull/269403
My name is not “https ://github.com/NixOS/nixpkgs/pull/269403”, and “Silvan Mosberger silvan.mosberger@tweag.io” is not the author of parallel.nix
as the commit claims.
@rhendric, when you quote a post you’re not supposed to edit what you’re quoting.
From the git commit headers:
commit 4874faf540622570ffc1ab545c05080ebe54b974 (HEAD -> infinisil)
Author: Silvan Mosberger <silvan.mosberger@tweag.io>
Date: Thu Nov 14 23:14:20 2024 +0100
[WIP] Parallel GH actions workflow for Nixpkgs eval
Partly taken from https://github.com/NixOS/nixpkgs/pull/352808 and https://github.com/NixOS/nixpkgs/pull/269403
My name is not “https ://github.com/NixOS/nixpkgs/pull/269403”, and “Silvan Mosberger silvan.mosberger@tweag.io” is not the author of parallel.nix
as the commit claims.
@rhendric, when you quote a post you’re not supposed to edit what you’re quoting.
I’m a bit upset that you’re immediately suspecting bad faith, but it’s okay, I also wouldn’t like it if it seems like others are ripping off my work. To clarify:
These posts were flagged as off-topic (and various other things) in the original thread. However, there seems to be a genuine issue underneath the complaint, that needs space to be resolved. I don’t want the posts hidden; the issue should be resolved, constructively, in this separate thread.
The snide tone of the original complaint, @amjoseph, doesn’t seem to have helped.