all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-30 1463434907e: ; Eliminate C++ comments and typo
Date: Sun, 18 Aug 2024 07:45:48 +0300	[thread overview]
Message-ID: <86a5ha1ls3.fsf@gnu.org> (raw)
In-Reply-To: <87cym6iudb.fsf@yahoo.com> (message from Po Lu on Sun, 18 Aug 2024 07:48:16 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 18 Aug 2024 07:48:16 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >>     ; Eliminate more C++ comments
> >>     
> >>     * lib-src/movemail.c:
> >>     
> >>     * nt/preprep.c (main):
> >>     
> >>     * src/unexw32.c (unexec): Convert C++-style comments to C.
> >
> > Why on earth are these cleanups being done on the release branch?
> > Cleanups are _never_ done there!  Please don't do anything like that
> > on the release branch, certainly not without asking first!!
> 
> These aren't code changes, only doc changes.

Comment style has nothing to do with documentation.  More importantly,
these are not improvements or bugfixes in any sense of those words
that is applicable to a release branch.  Please don't do anything like
that on the release branch in the future, certainly not without asking.



      reply	other threads:[~2024-08-18  4:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172390329286.25071.13652148232082952035@vcs2.savannah.gnu.org>
     [not found] ` <20240817140133.2E323C2BC70@vcs2.savannah.gnu.org>
2024-08-17 16:37   ` emacs-30 1463434907e: ; Eliminate C++ comments and typo Eli Zaretskii
2024-08-17 23:48     ` Po Lu
2024-08-18  4:45       ` Eli Zaretskii [this message]

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=86a5ha1ls3.fsf@gnu.org \
    --to=eliz@gnu.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 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.