unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40759@debbugs.gnu.org, posh18@pirilampo.be,
	monnier@iro.umontreal.ca, egrep@protonmail.ch, dgutov@yandex.ru
Subject: bug#40759: 26.3; Update Leuven-theme in Emacs dev trunk
Date: Mon, 04 May 2020 17:11:34 +0200	[thread overview]
Message-ID: <87tv0vag61.fsf@stefankangas.se> (raw)
In-Reply-To: <831rnzoigf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 May 2020 17:58:24 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Frankly, I'm a bit afraid that such a significant deviation from the
> practice of themes should be added to the release branch now.
> Stefan's opinion notwithstanding, there can always be something we are
> overlooking.

Thank you.  I will allow a couple of days before I push this to
master, in case anyone has any further comments.  We should be able to
fix any problems that pop up in time before 28.1 is released.

Best regards,
Stefan Kangas





  reply	other threads:[~2020-05-04 15:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  5:31 bug#40759: 26.3; Update Leuven-theme in Emacs dev trunk Fab Rice
2020-04-22  6:10 ` Stefan Kangas
2020-04-22 19:58 ` Fab Rice
2020-04-23 18:47   ` Stefan Kangas
2020-04-24 10:57 ` Serghei via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-04-24 11:26   ` Eli Zaretskii
2020-04-24 12:09     ` Fab Rice
2020-04-25  8:49       ` Eli Zaretskii
2020-04-25 14:36         ` Dmitry Gutov
2020-05-04 12:35           ` Stefan Kangas
2020-05-04 14:58             ` Eli Zaretskii
2020-05-04 15:11               ` Stefan Kangas [this message]
2020-05-09 16:48       ` Stefan Kangas
2020-05-13 17:36         ` Fab Rice
2020-08-08 12:23           ` 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=87tv0vag61.fsf@stefankangas.se \
    --to=stefan@marxist.se \
    --cc=40759@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=egrep@protonmail.ch \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=posh18@pirilampo.be \
    /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).