Post B5gtG7BrhAOeSO07iy by mirabilos@toot.mirbsd.org
 (DIR) More posts by mirabilos@toot.mirbsd.org
 (DIR) Post #B5fZOvFHHcTLm7Yl0a by rqm@exquisite.social
       0 likes, 0 repeats
       
       $ ssh puffy@fishtank.openbsd.amsterdamThe fishtank already runs the latest snapshot on -current, all locked and loaded for the imminent release of 7.9!#OpenBSD #79hype #RunBSD@OpenBSDAms @mischa
       
 (DIR) Post #B5fZOvWeF2Modzgd5E by h3artbl33d@exquisite.social
       0 likes, 0 repeats
       
       @rqm @OpenBSDAms @mischa already runs the latest snapshot on -current, all locked and loaded for the imminent release of 7.9!So does OpenBSDonApple.wiki!
       
 (DIR) Post #B5fZOvgvcoaf9sUq6i by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @h3artbl33d @rqm @OpenBSDAms @mischa will be fun once you discover that, sometimes, snapshots are newer than the release that comes after, or contain uncommitted changes
       
 (DIR) Post #B5gjLxYHRd2sl9dM6y by h3artbl33d@exquisite.social
       0 likes, 0 repeats
       
       @mirabilos @rqm @OpenBSDAms @mischa Haha I live and breath snapshots. Both on my daily drivers and some production infrastructure. That the snapshot of the 20 april might contain stuff that won't make it to -release is hardly new to me :)
       
 (DIR) Post #B5gjLxkKiogdMXGytk by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @rqm @h3artbl33d @OpenBSDAms @mischa just delete tmux then
       
 (DIR) Post #B5grh1asPZQP0fP5vM by h3artbl33d@exquisite.social
       0 likes, 0 repeats
       
       @mirabilos @rqm @OpenBSDAms @mischa Why?
       
 (DIR) Post #B5grh1w98URG4dM54q by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @rqm @mischa @h3artbl33d @OpenBSDAms contains slop vommits
       
 (DIR) Post #B5gtG6wyaWUFiD2EW8 by h3artbl33d@exquisite.social
       0 likes, 0 repeats
       
       @mirabilos @rqm @mischa @OpenBSDAms Ah yeah, couldn't follow the initial train of thought - going from OpenBSD snaps/releases to why tmux should be uninstalled. I just taken a quick look and wasn't able to say with certainty that tmux in OpenBSD accepted that slop.
       
 (DIR) Post #B5gtG7BrhAOeSO07iy by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @rqm @mischa @h3artbl33d @OpenBSDAms they did, five or so revisions ago for one of the files; this is because OpenBSD CVS is the primary repo for tmux and the tmux maintainer just actively chose to ignore what policy they already had and committed it and nobody even wants to address it despite multiple requests on the mailing list