Andreas Enge <andr...@enge.fr> writes: > Am Sun, Jul 13, 2025 at 10:14:16PM +0000 schrieb Attila Lendvai: >> this is somewhat tangential, but guix is the first project in my entire >> programmer career where it's not only allowed to commit changes that will >> break >> things, but it's straight out demanded (the one commit per package policy, >> even >> if it knowingly introduces incompatibilities).
There are many projects that do not have working CI, that sometimes do not build, that sometimes have broken parts. Either you are very lucky in picking projects to participate in, or in Guix it is just slightly more exposed due to the rolling nature and the number of contributors. > Well, that is rather misrepresenting things. It is recommended to push > such a series of commits at the same time. So people doing "guix pull" > should always end up on a working combination. Of course, one can then > take extraordinary steps to time travel on purpose in the middle of such > commits, but usually it is quite obvious that they come in a series. I am not sure `git bisect' can be considered "extraordinary steps". It is quite handy tool. So while it is fine from the user's point of view, series with middle being broken is somewhat unpleasant for developers. > And if possible, I still try to order the commits so that they do not > break anything. This is much appreciated, but I do not believe it is an actual policy? Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
