| 23 Feb 2026 |
 @acidbong:envs.net | In reply to @aiya:catgirl.cloud
i understand that PR titles are for the affected titles but my question is for conventions on branch names: if i want to merge a PR into haskell-updates, what should my branch name be? must it start with haskell-updates? (i.e. haskell-updates-fix-pkg versus fix-pkg
I believe head:haskell-updates filters for all PRs targeting the haskell-updates branch
i believe that would be base:haskell-updates, head filters on your branch name your branch name doesn't matter at all, only commit and PR description and contents | 20:12:06 |
| @acidbong:envs.net | * your branch name doesn't matter at all, only commit and PR description and contents, and the branch you're targeting | 20:13:29 |
|  @magpi:matrix.org changed their display name from magpi to Luke Worth. | 21:17:08 |
| @magpi:matrix.org changed their display name from Luke Worth to Luke. | 21:17:40 |
| 24 Feb 2026 |
|  Jack changed their profile picture. | 03:32:21 |
| 25 Feb 2026 |
 sterni | chreekat: I'm wondering now if you'll be quicker to redeploy all-cabal-tool or I in migrating hackage2nix to the cabal-install db :p | 17:23:53 |
| sterni | * chreekat: I'm wondering now whether you'll be quicker to redeploy all-cabal-tool or I in migrating hackage2nix to the cabal-install db :p | 17:24:08 |
 chreekat | fun idea | 17:47:47 |
| chreekat | i'll deploy tomorrow :p | 17:47:54 |
| chreekat | i have another client whose whole system just exploded for god knows why. keeps me occupied | 17:48:16 |
 maralorn | Probably a client who pays better than us. (Seeing that we are not paying you at all.) 😄 | 17:49:58 |
| chreekat | HF pays :3 | 18:16:49 |
| maralorn | Probably still not as good as the other client. 😆 | 18:21:56 |
|  Ember Void changed their display name from Void Mona(d) to Void Ember. | 19:11:27 |
| 26 Feb 2026 |
| chreekat | sterni: https://github.com/commercialhaskell/all-cabal-hashes/commit/e89f69681f6366e77ab017b8b496c4ee2c6825b5 | 10:19:40 |
| sterni | great thank you! did not get my change cleaned up in time… | 11:44:39 |
| chreekat | You should use casa! It also needs an update, but it's the superior, undocumented choice to all-cabal-hashes imo | 12:37:51 |
| chreekat | I'm gonna get it (casa.stackage.org) up to speed next | 12:38:33 |
| sterni | is it documented anywhere? | 13:42:26 |
| sterni | but I do not think we actually need it, the hackage index has everything we need nowadays as long as the index state timestamp is reliable but should be ok | 13:43:03 |
| chreekat | Just a couple old blog posts | 13:44:51 |
| chreekat | Interesting. I did not know you could just go straight to hackage now. I know that casa solved problems when it was developed, the same problems all-cabal-hashes was supposed to solve | 13:50:12 |
 teo (they/he) | I think the issue that all-cabal-hashes solves (for nix) is that you want to map a package name and revision to a cabal file hash at nix eval time, which I don't think you can do with casa without IFD | 14:29:34 |
| chreekat | True, you probably need dynamic drvs in order to follow the chain from a fod that pulls the top of the tree to all the other fods that describe the package source | 15:25:26 |
| maralorn | Dynamic drvs are not allowed on hydra, are they? | 15:27:14 |
| chreekat | I assume not, but at least it's theoretically more pleasing than ifd | 15:36:57 |
| chreekat | So, I will carry on dreaming 😄 | 15:37:30 |
 toonn | Recursive Nix was another such dream. | 16:00:06 |
| maralorn | Isn’t even basically the same? | 16:10:26 |
| toonn | Both of them and IFD basically achieve the same thing AFAIK. | 16:12:31 |
