From: "João Távora" <joaotavora@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Dmitry Gutov <dmitry@gutov.dev>, emacs-devel@gnu.org
Subject: Re: master 78fc49407b8 1/3: Improve filling of ChangeLog entries
Date: Wed, 31 Jan 2024 13:22:38 +0000 [thread overview]
Message-ID: <CALDnm536W=Lw0wMT8gjxgX8Y8m47+5WSBE65dgP+M3bDYa_60w@mail.gmail.com> (raw)
In-Reply-To: <878r45px71.fsf@yahoo.com>
On Wed, Jan 31, 2024 at 11:19 AM Po Lu <luangruo@yahoo.com> wrote:
> I don't doubt that these particular `cl-loop' or `pcase'
> forms are simple to understand, provided that the reader takes the ten
> or so minutes to absorb the relevant portions of their documentation.
As I said, I'd just use edebug or macroexpand these things away, like
I did. You do know edebug, right? And pp-macroexpand? The latter
takes not even 10 seconds, what 10 minutes!??
Also, do you have any remote idea how much time it will take someone
to read your code which has grown those functions 3 or 4 fold??
> avocational projects such as Emacs, where I make a mental note of tasks
> that interest me, and pick the least time-consuming of them to complete
> whenever free time (which, surprising as it may be, is scarce) does come
> my way.
Judging by the number of follow-up bugfix commits, you misjudged that
badly.
> Which is also the reason I requested no more than that you not install
> your version now, leaving the door open to future improvement on your
> terms once I finish making it work.
Of course not, it's now yours. Probably forever.
The unit tests are basically the only thing I can read from
your code. Really, in practice you'll be probably be the only one ever
reading that long-winded Fotran-like code, so I wish you stick around
for a long time maintaining it.
The only "improvement" I'd have is reverting all your work and
applying my succinct patch that meets the current goalposts.
If you move them or invent new ones that's another matter... hopefully
that will also come with tests, or even some minimal discussion.
So while the code would go back to being simpler (even without cl-loop)
you'd probably be demotivated to keep maintaing the file. Also
the history is already botched, I'd just make it worse. Really doesn't
justify rewriting your code. It'd be a poor, almost ridiculous, way to
"collaborate".
> diatribe was unnecessary (and I'm not certain I disagree with
> most of it)
If, in all that sea of bravado, it has dropped a grain of self-doubt
for next time you're pulling out the bulldozer, I consider it a diatribe
well tribed.
Anyway, have fun, and all the best
João
next prev parent reply other threads:[~2024-01-31 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170643232559.30479.16631610453249222615@vcs2.savannah.gnu.org>
[not found] ` <20240128085846.187A2C1DAE4@vcs2.savannah.gnu.org>
2024-01-28 13:22 ` master 78fc49407b8 1/3: Improve filling of ChangeLog entries Dmitry Gutov
2024-01-28 13:37 ` Po Lu
2024-01-30 22:07 ` João Távora
2024-01-31 6:43 ` Po Lu
2024-01-31 10:28 ` João Távora
2024-01-31 11:19 ` Po Lu
2024-01-31 13:22 ` João Távora [this message]
2024-01-31 14:01 ` Po Lu
2024-01-31 14:30 ` João Távora
2024-01-31 15:15 ` Dmitry Gutov
2024-01-31 15:32 ` Alan Mackenzie
2024-01-31 16:46 ` João Távora
2024-01-31 18:29 ` Alan Mackenzie
2024-01-31 17:05 ` Dmitry Gutov
2024-01-31 18:45 ` Alan Mackenzie
2024-01-31 20:39 ` Dmitry Gutov
2024-01-29 20:13 ` Stefan Kangas
2024-01-30 1:26 ` Po Lu
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='CALDnm536W=Lw0wMT8gjxgX8Y8m47+5WSBE65dgP+M3bDYa_60w@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
/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.