| 22 Jan 2026 |
 John Ericson | does your new source accessor need any more file-descriptor functions? | 20:28:41 |
| John Ericson | or was readLinkAt the last one? | 20:28:49 |
| John Ericson | Sergei Zimmerman (xokdvium): did you fix the freebsd 25.11 error btw? | 20:35:48 |
| John Ericson | because we could do that | 20:35:57 |
| 23 Jan 2026 |
 Robert Hensing (roberth) | Did anyone have a problem with mixed pipe operators being allowed, or hear anyone complain about it?
E.g. a |> b <| c or p <| q |> r for some expressions a, b, etc.
If not, I'll propose FCP as RFC 148 shepherd. | 00:17:10 |
|  Jeronimo changed their display name from Jeroen Jeurissen to Jeronimo. | 12:22:29 |
| John Ericson | fine with me! | 19:11:32 |
|  silent_water joined the room. | 19:12:41 |
|  fcainzos joined the room. | 21:57:24 |
| 24 Jan 2026 |
 faukah | What is the behavior of the --commit-lock-file flag? Does it only commit the change when the invoked command actually changes the flake.lock? Or is it sufficient to have a flake.lock file that is modified in the current git staging area? | 20:31:38 |
| 25 Jan 2026 |
 Mindavi | In reply to @faukah:faukah.com
What is the behavior of the --commit-lock-file flag? Does it only commit the change when the invoked command actually changes the flake.lock? Or is it sufficient to have a flake.lock file that is modified in the current git staging area? Pretty sure it only does something if the update command results in an update | 00:30:00 |
| Mindavi | But I think it should be fairly easy to try out to be sure | 00:30:40 |
