bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13


From: Protesilaos Stavrou
Subject: bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0
Date: Mon, 12 Oct 2020 09:37:02 +0300

Commit c1b0515952 to Emacs 'master' on August 27 added two new themes.
Their version was 0.12.0.  A new version is now available, as well as a
texinfo file that documents all their customisation options.  Please see
the attached patch.

Now some administrative considerations:

+ The two themes are also available in GNU ELPA.  What is the best way
  to ensure that we sync between emacs.git and elpa.git?  GNU ELPA has
  hitherto pulled from dedicated branches on my upstream git repository.
  Maybe it would be better/easier to start building directly from the
  Emacs source?  This would reduce the overall workload.

+ Sending attachments with large diffs has the downside of losing the
  commit history.  Do Emacs maintainers wish to keep track of it?  If
  so, what would be the best way to preserve it, seeing as I am
  developing them on my own upstream?  For context, the Leuven theme,
  which is also developed externally, only gets updated in relatively
  large increments, such as in commits to Emacs 'master' 99f8a1c917,
  b5ccc1beb3, and 95e509140e.

+ Should the texinfo file be mentioned in the NEWS entry about the two
  themes?  The attached patch does not include such a change.

I am prepared to do whatever the maintainers consider necessary.  Thank
you for your time!

Best regards,
Protesilaos

-- 
Protesilaos Stavrou
protesilaos.com

Attachment: 0001-Update-modus-operandi-modus-vivendi-to-0.13.0.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]