From: Eli Zaretskii <eliz@gnu.org>
To: dick <dick.r.chiang@gmail.com>
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 15:28:12 +0200 [thread overview]
Message-ID: <83pmq2neab.fsf@gnu.org> (raw)
In-Reply-To: <87h7be6lej.fsf@dick> (message from dick on Sun, 12 Dec 2021 07:46:28 -0500)
> From: dick <dick.r.chiang@gmail.com>
> Cc: larsi@gnus.org, 52440@debbugs.gnu.org
> Date: Sun, 12 Dec 2021 07:46:28 -0500
>
> > Triggering unnecessary rebuilds is an annoyance during development
>
> I don't see how keeping the three functions in lisp.h versus sqlite.h
> makes triggering the world any less frequent.
It's the other way around: separating them will NOT make rebuilds less
frequent. So it's kinda fruitless, as separations go.
> And besides, I find myself *constantly* having to `git clean -dfX` and
> remake the world on account of:
>
> Error: Recursive load: "...international/uni-special-lowercase.el"
Doesn't happen here, never did.
> Your marshalling of the recompilation nuisance is formulaic
> straw-grasping to get one's way. I know because I often use the same
> rhetorical device.
You are evidently talking about yourself, so don't expect me to assign
any significance to that. Doesn't help your prestige around here,
which is already pretty low.
next prev parent reply other threads:[~2021-12-12 13:28 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 [this message]
2021-12-12 14:25 ` dick
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pmq2neab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52440@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.