From: Stefan Kangas <stefankangas@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>,
Protesilaos Stavrou <info@protesilaos.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 16:59:23 +0000 [thread overview]
Message-ID: <CADwFkmmV4dRe2GkqoGhyaHFZ8WrLrqtV36iMdK+xdWMsA9JEvA@mail.gmail.com> (raw)
In-Reply-To: <87r1punpih.fsf@tcd.ie>
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> I'm in no hurry - the only reason I asked you instead of fixing it
> myself, is that I saw you were already in the process of applying
> feedback, and I didn't have the time to look into regenerating the
> Texinfo manual from Org.
This was fixed in Protesilaos' follow-up commit 4970e2c7ea.
next prev parent reply other threads:[~2020-10-19 16:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <draft-87v9ffz1wx.fsf@stefankangas.se>
2020-10-16 13:46 ` bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0 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 [this message]
2020-10-19 17:12 ` Basil L. Contovounesios
2020-10-12 6:37 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
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
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=CADwFkmmV4dRe2GkqoGhyaHFZ8WrLrqtV36iMdK+xdWMsA9JEvA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=43944@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=info@protesilaos.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.