4 ms·
> > 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
by anarazel 3y ago
> > 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...
- tristan957 3y agoMy 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/.config/aerc/filters/pg-wtf https://git.sr.ht/~tristan957/dotfiles/tree/master/item/aerc...
- anarazel 3y agoYea. 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...