From: David Kastrup <dak@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 5022e27: ; Do not overwrite preexisting contents of unread-command-events
Date: Sat, 08 Aug 2015 10:33:17 +0200 [thread overview]
Message-ID: <87k2t6i3hu.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r3nj3vbw.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 04 Aug 2015 17:52:03 +0200")
David Kastrup <dak@gnu.org> writes:
> Glenn Morris <rgm@gnu.org> writes:
>
>> David Kastrup wrote:
>>
>>> branch: master
>>> commit 5022e27dac4c13651941e425dbec5b3a2cecdae4
>>> Author: David Kastrup <dak@gnu.org>
>>> Commit: David Kastrup <dak@gnu.org>
>>>
>>> ; Do not overwrite preexisting contents of unread-command-events
>>
>> Surely this change deserved to create a ChangeLog entry, rather than
>> being marked with "; " to exclude that.
>
> It's a sort of a janitorial potential bug fix for symptoms nobody
> complained about yet, distributed around dozens of files and disparate
> functions in various parts of Emacs. I've posted the patch more than a
> week ago on emacs-devel. No comment. I put out a reminder yesterday
> that I was going to push this patch. No comment.
>
> A ChangeLog entry would run over several dozens of lines and take the
> better part of an hour to create since C-x v a does not work with Git.
> I figured that nobody would even notice anyway.
>
> What do you propose I do now?
That question was not rhetorical. I admit that the leadup may not have
been the best incentive for answering it. Sorry for that. What I was
saying was that my own judgment was that the next consistent option
would have been a significant investment of effort that I saw no
compelling justification for, so I shopped for other opinions without
result.
You disagree, but I don't see your take on "next consistent option".
I am not opposed to investing a significant additional amount of time
for meeting a reasonable project objective. But I don't want to waste
that time based on guesswork that might end wide off the mark.
--
David Kastrup
next prev parent reply other threads:[~2015-08-08 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150804124300.13374.78396@vcs.savannah.gnu.org>
[not found] ` <E1ZMbYa-0003UO-69@vcs.savannah.gnu.org>
2015-08-04 15:30 ` master 5022e27: ; Do not overwrite preexisting contents of unread-command-events Glenn Morris
2015-08-04 15:52 ` David Kastrup
2015-08-08 8:33 ` David Kastrup [this message]
2015-08-08 9:11 ` Eli Zaretskii
2015-08-08 9:38 ` David Kastrup
2015-08-08 10:18 ` Eli Zaretskii
2015-08-08 14:17 ` Stefan Monnier
2015-08-08 15:04 ` David Kastrup
2015-08-08 16:08 ` David Kastrup
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=87k2t6i3hu.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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.