News for hackers. Stuff that matters.
Re:Postgres: The Next Generation by anarazel on Wednesday October 11, 2023 @11:08AM (#37845419)
> > I find lkml style patch handling bad as well, particularly with every patchset revision getting its own thread. Very easy to loose track.

> This is a good point, but if it works for the largest open-source software project in the world, I think it could work for Postgres too. I find that being able to reply inline to an email without having to copy-paste huge sections of an attachment is pretty valuable.

I had actually forgotten that issue, having scripted it years and years ago to be automatic. My beef around this is gmail attachment being randomly ordered...

Re:Postgres: The Next Generation by tristan957 on Friday October 13, 2023 @11:44AM (#37871875)
My beef with gmail is that it completely destroys mimetypes. Everything that gmail postgres contributors send (from the web interface) seems to always be application/octet-stream, which is really annoying for configuring my email client.

https://git.sr.ht/~tristan957/dotfiles/tree/master/item/aerc...

Re:Postgres: The Next Generation by anarazel on Friday October 13, 2023 @01:43PM (#37873351)
Yea. I've long since given up on that ever being correct. Too many people with too many mail clients. Thus for many mime types I just force that to be redone:

  mime_lookup application/octet-stream application/x-gzip application/gzip application/x-bzip2 binary/octet-stream application/x-download invalid/octet-stream
Not that that's a good answer...