From: dick <dick.r.chiang@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52440@debbugs.gnu.org, larsi@gnus.org
Subject: bug#52440: 28.0.50; [PATCH] Quis custodiet ipsos custodes (sqlite3)
Date: Sun, 12 Dec 2021 09:25:13 -0500 [thread overview]
Message-ID: <87tufd529i.fsf@dick> (raw)
In-Reply-To: <83pmq2neab.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Dec 2021 15:28:12 +0200")
> It's the other way around: separating them will NOT make rebuilds less
> frequent. So it's kinda fruitless, as separations go.
Interesting. I just edited sqlite.h in my fork, and it didn't recompile
the world. So thanks for suggesting another reason why disaggregating
the sqlite junk from lisp.h is superior. Why thread.h is included in
lisp.h is a decision that predates me.
> Doesn't help your prestige around here, which is already pretty low.
Prestige? The path we've chosen -- slavishly obsessing over a last-century
text editor fast becoming extinct -- is quite possibly the least
prestigious endeavor I can think of. Affability is probably the word
you're looking for.
next prev parent reply other threads:[~2021-12-12 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 21:32 bug#52440: 28.0.50; [PATCH] Quis custodiet ipsos custodes (sqlite3) dick.r.chiang
2021-12-12 6:12 ` Lars Ingebrigtsen
2021-12-12 7:52 ` Eli Zaretskii
2021-12-12 11:32 ` dick
2021-12-12 12:01 ` Eli Zaretskii
2021-12-12 12:46 ` dick
2021-12-12 13:28 ` Eli Zaretskii
2021-12-12 14:25 ` dick [this message]
2021-12-12 14:38 ` Eli Zaretskii
2021-12-12 15:04 ` dick
2021-12-13 1:55 ` Phil Sainty
2021-12-12 11:49 ` Lars Ingebrigtsen
2021-12-12 12:04 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tufd529i.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=52440@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).