From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: contovob@tcd.ie, 41744@debbugs.gnu.org
Subject: bug#41744: 27.0.91; Various D-Bus cleanups
Date: Mon, 08 Jun 2020 17:48:03 +0300 [thread overview]
Message-ID: <83mu5d7gws.fsf@gnu.org> (raw)
In-Reply-To: <874krln7fg.fsf@gmx.de> (message from Michael Albinus on Mon, 08 Jun 2020 13:06:11 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Mon, 08 Jun 2020 13:06:11 +0200
> Cc: 41744@debbugs.gnu.org
>
> > I propose these documentation cleanups for emacs-27:
>
> In general, I agree with your changes. However, they are so large that I
> don't know whether they shall go into the emacs-27 branch. To be decided
> by Eli, I guess.
Documentation changes are inherently safe. So if you (Michael) think
the changes are for the better, go ahead and install on the release
branch. If you aren't sure, e.g. if you think that some of the
changes might be controversial, then master it is. I cannot tell
which one is it because I know almost nothing about D-Bus. But if
there are specific questions regarding specific parts of the text, I
can try helping you make the decision, if you need help.
next prev parent reply other threads:[~2020-06-08 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 23:26 bug#41744: 27.0.91; Various D-Bus cleanups Basil L. Contovounesios
2020-06-08 11:06 ` Michael Albinus
2020-06-08 14:00 ` Basil L. Contovounesios
2020-06-08 14:20 ` Michael Albinus
2020-06-08 14:48 ` Eli Zaretskii [this message]
2020-06-08 14:52 ` Michael Albinus
2020-06-08 17:28 ` Basil L. Contovounesios
2020-06-17 20:08 ` Basil L. Contovounesios
2020-06-18 9:59 ` Michael Albinus
2020-06-18 15:34 ` Basil L. Contovounesios
2020-06-18 16:59 ` Michael Albinus
2020-06-18 17:05 ` Basil L. Contovounesios
2020-06-18 18:02 ` Michael Albinus
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=83mu5d7gws.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41744@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=michael.albinus@gmx.de \
/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.