From: jared--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Additional xterm-mouse cleanup
Date: Wed, 03 Feb 2021 22:57:23 -0800 [thread overview]
Message-ID: <e495df7888a8f71f44febe2d177e9608@finder.org> (raw)
In-Reply-To: <83k0rq5wxm.fsf@gnu.org>
On 2021-02-02 7:08 am, Eli Zaretskii wrote:
>> Date: Tue, 02 Feb 2021 00:28:24 -0800
>> From: Jared Finder <jared@finder.org>
>> Cc: emacs-devel@gnu.org
>>
>> > P.S. Please in the future post patches via "M-x report-emacs-bug", so
>> > that our issue tracker records all the pertinent discussions.
>>
>> Sorry about that.
>
> No need to apologize, no disaster happened.
>
>> I guess I should delete most of the template text if is just
>> straightforward feature dev. Is that right?
>
> Yes, if the change you propose is not for some issue that is specific
> to the platform on which you write the message.
Okay, I will do that for future changes. Let me know if I should move
this thread to report-emacs-bug as well. My current plan is to finish
off the two changes that are nearly done and not controversial (i.e.,
not the change to read_key_sequence), and then have all future changes
done via report-emacs-bug.
-- MJF
next prev parent reply other threads:[~2021-02-04 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 6:32 Additional xterm-mouse cleanup jared--- via Emacs development discussions.
2021-01-28 14:25 ` Stefan Monnier
2021-02-02 8:24 ` jared--- via Emacs development discussions.
2021-02-02 14:37 ` Stefan Monnier
2021-02-04 6:54 ` jared--- via Emacs development discussions.
2021-02-15 1:02 ` Jared Finder via Emacs development discussions.
2021-02-25 3:56 ` Stefan Monnier
2021-02-25 6:08 ` Jared Finder via Emacs development discussions.
2021-02-25 13:52 ` Stefan Monnier
2021-01-30 9:38 ` Eli Zaretskii
2021-02-02 8:28 ` jared--- via Emacs development discussions.
2021-02-02 15:08 ` Eli Zaretskii
2021-02-04 6:57 ` jared--- via Emacs development discussions. [this message]
2021-02-04 15: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=e495df7888a8f71f44febe2d177e9608@finder.org \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=jared@finder.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.