From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: master 501e2096d6: Fix some issues with a recent change
Date: Mon, 27 Dec 2021 16:40:46 +0200 [thread overview]
Message-ID: <d90adb33-49fe-89ec-af26-7d91a004a93c@yandex.ru> (raw)
In-Reply-To: <837dbqohgz.fsf@gnu.org>
On 27.12.2021 06:27, Eli Zaretskii wrote:
> I find it entirely pertinent. Changes aren't supposed to be judged by
> reading the emacs-diffs mailing list, they are supposed to be judged
> by looking at the VCS logs, in which case the "recent change" part
> will tell you all you need to know.
>
> Once again, personal workflows should not affect our coding
> conventions.
"Everybody has to read everything" is a common problem (both regarding
diffs and the bug tracker), so it would be helpful to alter our
workflows somehow.
next prev parent reply other threads:[~2021-12-27 14:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164051393145.21885.8315099612759503047@vcs2.savannah.gnu.org>
[not found] ` <20211226101851.B61E5C04DCC@vcs2.savannah.gnu.org>
2021-12-26 17:04 ` master 501e2096d6: Fix some issues with a recent change Stefan Monnier
2021-12-26 18:18 ` Eli Zaretskii
2021-12-26 21:12 ` Stefan Monnier
2021-12-27 0:56 ` Po Lu
2021-12-27 4:22 ` Stefan Monnier
2021-12-27 5:01 ` Po Lu
2021-12-27 6:14 ` Stefan Monnier
2021-12-27 6:19 ` Po Lu
2021-12-27 12:07 ` Óscar Fuentes
2021-12-27 20:18 ` Stefan Monnier
2021-12-27 23:19 ` Stefan Kangas
2021-12-28 3:25 ` Eli Zaretskii
2021-12-28 3:48 ` Stefan Kangas
2021-12-27 16:20 ` [External] : " Drew Adams
2021-12-27 3:27 ` Eli Zaretskii
2021-12-27 4:27 ` Stefan Monnier
2021-12-27 14:31 ` Eli Zaretskii
2021-12-27 14:40 ` Dmitry Gutov [this message]
2021-12-27 12:08 ` Lars Ingebrigtsen
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=d90adb33-49fe-89ec-af26-7d91a004a93c@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).