From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: ulm@gentoo.org, emacs-devel@gnu.org
Subject: Re: emacs-29 82d6bb66fea 4/5: Update HISTORY and ChangeLog.4
Date: Sun, 23 Jul 2023 17:00:55 +0300 [thread overview]
Message-ID: <83h6puu3qg.fsf@gnu.org> (raw)
In-Reply-To: <87v8eayc3d.fsf@gmx.de> (message from Michael Albinus on Sun, 23 Jul 2023 15:46:46 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Sun, 23 Jul 2023 15:46:46 +0200
>
> What about this compromise: we change HISTORY in the emacs-29 branch. If
> there is a need for an RC2, this change will be part of it. Otherwise,
> it will appear with Emacs 29.2.
I already changed it. I have no energy left for these meaningless
arguments.
I just cannot stop wondering why people keep arguing about these
minor, almost meaningless issues after their opinions were heard and
disagreed upon. Just accept the decision and move on. But nooo....
So now I will have to regenerate a tarball instead of reusing the same
one. Another hour of my time. No one cares but me, I know. What
matters is that they got what they wanted.
next prev parent reply other threads:[~2023-07-23 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169010084365.28212.10109850313190874289@vcs2.savannah.gnu.org>
[not found] ` <20230723082725.62A5BC138F4@vcs2.savannah.gnu.org>
2023-07-23 10:52 ` emacs-29 82d6bb66fea 4/5: Update HISTORY and ChangeLog.4 Michael Albinus
2023-07-23 11:21 ` Eli Zaretskii
2023-07-23 12:34 ` Ulrich Mueller
2023-07-23 12:53 ` Eli Zaretskii
2023-07-23 13:02 ` Ulrich Mueller
2023-07-23 13:26 ` Po Lu
2023-07-23 13:48 ` Michael Albinus
2023-07-23 13:46 ` Michael Albinus
2023-07-23 14:00 ` Eli Zaretskii [this message]
2023-07-23 14:05 ` Michael Albinus
2023-07-23 14:07 ` Ulrich Mueller
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=83h6puu3qg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=ulm@gentoo.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.