From: Protesilaos Stavrou <info@protesilaos.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 43944@debbugs.gnu.org
Subject: bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0
Date: Mon, 19 Oct 2020 11:12:01 +0300 [thread overview]
Message-ID: <874kmqbpny.fsf@protesilaos.com> (raw)
In-Reply-To: <CADwFkmn8UwBQRdZbwUQ=8VNS7JUbssvnOhKZJvHESwNnShULfg@mail.gmail.com> (Stefan Kangas's message of "Sat, 17 Oct 2020 16:23:30 +0000")
On 2020-10-17, 16:23 +0000, Stefan Kangas <stefankangas@gmail.com> wrote:
> Protesilaos Stavrou <info@protesilaos.com> writes:
>
>> "Build" is the wrong term here. Sorry about that! My intent is to find
>> an easy way/workflow to get the files from Emacs into GNU ELPA.
>>
>> And by "easy" I mean not to duplicate the work we do here. So I would
>> not have to contact the GNU ELPA maintainers separately and have them
>> pull from my git source.
>
> Right. Hmm, it's a bit tricky to be honest, because there are several
> options and AFAICT the workflows are not exactly 100 % streamlined in
> all cases. Maybe you could bring this question to emacs-devel?
Yes, I shall post on emacs-devel.
>> I attach a possible rewording that also corrects "colour" and adds an
>> explicit reference to the WCAG AAA accessibility spec. Please note that
>> I do not know how to properly reference an Info node: I used 'C-u 0 x',
>> which calls 'Info-copy-current-node-name'.
>
> Great, thanks. I made some minor changes and pushed it to master as
> commit 00c4d982e8.
Thank you!
--
Protesilaos Stavrou
protesilaos.com
next prev parent reply other threads:[~2020-10-19 8:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 6:37 bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0 Protesilaos Stavrou
2020-10-16 10:50 ` Stefan Kangas
2020-10-16 17:13 ` Stefan Kangas
2020-10-17 7:13 ` Protesilaos Stavrou
2020-10-17 16:23 ` Stefan Kangas
2020-10-19 8:12 ` Protesilaos Stavrou [this message]
2020-10-19 12:18 ` Stefan Kangas
2020-10-19 12:31 ` Protesilaos Stavrou
2020-10-19 12:57 ` Protesilaos Stavrou
2020-10-19 15:42 ` Stefan Kangas
[not found] <draft-87v9ffz1wx.fsf@stefankangas.se>
2020-10-16 13:46 ` Stefan Kangas
2020-10-16 15:30 ` Eli Zaretskii
2020-10-16 20:39 ` Protesilaos Stavrou
2020-10-17 0:07 ` Stefan Kangas
2020-10-17 7:15 ` Protesilaos Stavrou
2020-10-17 7:13 ` Eli Zaretskii
2020-10-17 8:09 ` Protesilaos Stavrou
2020-10-17 8:59 ` Basil L. Contovounesios
2020-10-19 8:08 ` Protesilaos Stavrou
2020-10-19 16:34 ` Basil L. Contovounesios
2020-10-19 16:55 ` Protesilaos Stavrou
2020-10-19 17:11 ` Basil L. Contovounesios
2020-10-19 16:59 ` Stefan Kangas
2020-10-19 17:12 ` Basil L. Contovounesios
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=874kmqbpny.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=43944@debbugs.gnu.org \
--cc=stefankangas@gmail.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).