| 13 Dec 2021 |
 andi- | At least the cinny upgrade was just a npins update cinny for a new source build. | 16:16:49 |
 Andreas Rammhold | Deployed a new cinny and element-web version. | 16:23:53 |
 Mic92 (Old) | andi-: nix build -L is actually quite nice because it also shows the package that the log line is associated with. | 16:44:40 |
| Mic92 (Old) | I think nix build -L should be default because it's better than both nix build and nix-build | 16:45:09 |
| andi- | but if I build a single attribute and a single derivation I'd like to be able to see the log like it used to be. | 16:45:14 |
| Mic92 (Old) | You can also use it for a single derivation, but often enough even a single derivation can trigger the build of another derivation i.e. fetching source | 16:45:49 |
| andi- | And I am no longer willing to open issues on the Nix repo or PRs. It just doesn't have any impact on the development. | 16:45:56 |
| Mic92 (Old) | I this one was quite needed: https://github.com/NixOS/nix/pull/5747 | 16:46:53 |
| Mic92 (Old) | * I think this one was quite needed: https://github.com/NixOS/nix/pull/5747 | 16:47:45 |
| andi- | Yeah but Eelco will either comment that it isn't needed in the new CLI (which is experimental...) or that it doesn't cover enough cases or just merge it in a few weeks without a single comment. | 16:48:20 |
| Mic92 (Old) | I also found contributing to nix a bit frustrating, which is why I focused more on building tools around it. | 16:48:24 |
| andi- | I rather send messages to the LKML than contribute to Nix. The experience is a ton better. | 16:48:46 |
| andi- | The problem is just that the nix upgrades are kind of forced upon us at some point. | 16:49:07 |
| Mic92 (Old) | It's a bit hit and miss on LKML as well. | 16:49:15 |
| andi- | Oh yeah but at least there is someone to talk to and someone replies. | 16:49:28 |
| Mic92 (Old) | My qemu patch was also ignored completyly | 16:49:30 |
| Mic92 (Old) | * My qemu patch was also ignored completely | 16:49:44 |
| Mic92 (Old) | And having to read all emails in a thread in order to find out what the merge state of a patch is, is also exhausting. | 16:50:53 |
| andi- | There are some projects that just suck regardless of platform. I had a terrible experience trying to contribute to GRUB. Only after I pinged a co-worker of one of the maintainers on IRC I received feedback. | 16:50:54 |
| Mic92 (Old) | Any idea why patchwork does not show my patch here? https://patchwork.kernel.org/project/qemu-devel/list/?series=&submitter=200979&state=&q=&archive=&delegate= | 16:52:55 |
| Mic92 (Old) | subject: hw/i386: fix phys-bits on cpus with AMD SEV/SMD | 16:53:09 |
| andi- | https://patchwork.kernel.org/project/qemu-devel/list/?series=&submitter=200979&state=*&q=&archive=both&delegate= | 16:54:28 |
| Mic92 (Old) | If I wanted to respond to this email, since I deleted the original. How would I do that? | 16:55:58 |
| andi- | In-Reply-To: <0b3132692ee53e98082b4dd12e41b4a3@thalheim.io> | 16:56:32 |
| andi- | Add that mail header | 16:56:37 |
| andi- | Also: https://lore.kernel.org/all/0b3132692ee53e98082b4dd12e41b4a3@thalheim.io/#R | 16:57:15 |
| andi- | You could do that via git send-email | 16:57:24 |
| andi- | could you don't have to. | 16:57:39 |
| andi- | thunderbird might also just support that mailto: link at on that page | 16:58:42 |
| Mic92 (Old) | Seemed to work even in rainloop webmail :) | 17:01:13 |
