unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-29 b8d2ec920f: Revert "Improve last change to xfaces.c" (05ece1eb8b)
Date: Mon, 12 Dec 2022 09:09:43 +0000	[thread overview]
Message-ID: <ec23ed3e9549d2519192@heytings.org> (raw)
In-Reply-To: <87359ljq04.fsf@yahoo.com>


>> Don't do that!  You did not answer ANY part of what I said.

Of course I did.  That you did not read it is another thing.

>
> Btw, for posterity's sake, I undid this revert for two reasons:
>

What kind of development practice is this?  You "improve" code in a 
complex area of the Emacs code base that was agreed upon after a long 
discussion only a couple of hours after it was pushed, without asking 
anyone whether what you want to do is okay?  And you revert without even 
reading or replying to the detailed explanation why that "improvement" was 
wrong.

>
> - unsetting the "extra" attribute is not safe on the Haiku port.
>

That's wrong.  And you would have understood this if you had read the 
detailed explanation why your "improvement" is wrong.

>
> - the bitmask variable is a real nusiance for anyone trying to debug 
> Emacs or change the layout of the font attribute index enumerator.
>

It isn't, and it is not supposed to be modified on a daily basis.

>
> Just because a bug has been closed does NOT mean the change in it is no 
> longer subject to scrutiny. I don't follow bug reports that aren't 
> related to X, which means I (and possibly many others) only see changes 
> as they arrive on emacs-diffs.  Which means that by the time the bug is 
> closed, no, the discussion is not ``over'', and other people still have 
> a chance to make changes to problems they see as they see them (a 
> bitmask depending on the internal layout of an enum exposed to Lisp is 
> definitely one such problem, so is unsetting `:extra'.)
>

Nobody said the discussion was over (although I was hoping it was).

But what you did is not a "discussion", it is the exact opposite of a 
"discussion": these are misguided changes introduced in the release branch 
_without any discussion_.




  reply	other threads:[~2022-12-12  9:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167080778504.14972.16819452979975432761@vcs2.savannah.gnu.org>
     [not found] ` <20221212011625.58E8AC004B4@vcs2.savannah.gnu.org>
2022-12-12  2:41   ` emacs-29 b8d2ec920f: Revert "Improve last change to xfaces.c" (05ece1eb8b) Po Lu
2022-12-12  2:48     ` Po Lu
2022-12-12  9:09       ` Gregory Heytings [this message]
2022-12-12  9:37         ` Issue building master Ergus
2022-12-12 13:33           ` Eli Zaretskii
     [not found]             ` <2127787931.394320.1670853418624@mail.yahoo.com>
2022-12-12 14:12               ` Eli Zaretskii
2022-12-12 15:49                 ` Ergus
2022-12-12 16:04                   ` Eli Zaretskii
2022-12-12 17:16                     ` Ergus
2022-12-12 10:05         ` emacs-29 b8d2ec920f: Revert "Improve last change to xfaces.c" (05ece1eb8b) Po Lu
2022-12-12 10:42           ` Gregory Heytings
2022-12-12 11:08             ` Po Lu
2022-12-12 10:18     ` xenodasein--- via Emacs development discussions.
2022-12-12 10:29       ` Cool down, please [was: emacs-29 b8d2ec920f: Revert ...] tomas
2022-12-12 10:36       ` emacs-29 b8d2ec920f: Revert "Improve last change to xfaces.c" (05ece1eb8b) Po Lu
2022-12-12 10:48         ` xenodasein--- via Emacs development discussions.
2022-12-12 13:44       ` Eli Zaretskii
2022-12-12 15:03         ` xenodasein--- via Emacs development discussions.
2022-12-12 15:13           ` tomas

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=ec23ed3e9549d2519192@heytings.org \
    --to=gregory@heytings.org \
    --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 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).