unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: okamsn@protonmail.com, emacs-devel@gnu.org
Subject: Re: How to install documentation in sub-directory with Package VC?
Date: Wed, 12 Apr 2023 10:41:25 +0300	[thread overview]
Message-ID: <837cuh8s4a.fsf@gnu.org> (raw)
In-Reply-To: <87leix5zms.fsf@posteo.net> (message from Philip Kaludercic on Wed, 12 Apr 2023 07:27:23 +0000)

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: emacs-devel@gnu.org
> Date: Wed, 12 Apr 2023 07:27:23 +0000
> 
> Okamsn <okamsn@protonmail.com> writes:
> 
> > On 2023-04-10 13:39 UTC, Philip Kaludercic wrote:
> >> Just pinging to see if you want to finish this or if I should modify the
> >> patch?  Seeing as the Emacs 29 release is coming closer, I'd rather have
> >> this fixed sooner than later.
> >
> > Sorry about that.  Please see the attached file, and please modify as
> > you see fit.  I am happy with it, but my only opinion is that all of the
> > currently supported keys should be given in the manual, which this does.
> 
> This looks good to me.  Eli would you be ok with me pushing this to
> emacs-29?  There are no functional changes.

Documentation changes are always okay on the release branch.

> I found a few more passive phrases, which I attempted to reformulate.
> In case you think this is worth addressing, how does this sound:

LGTM, thanks.



  reply	other threads:[~2023-04-12  7:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  3:13 How to install documentation in sub-directory with Package VC? Okamsn
2023-03-14 15:56 ` Philip Kaludercic
2023-03-15  9:41   ` Philip Kaludercic
2023-03-16  1:37     ` Okamsn
2023-03-16  8:44       ` Philip Kaludercic
2023-03-28  1:50         ` Okamsn
2023-03-28  7:41           ` Philip Kaludercic
2023-04-02  0:41             ` Okamsn
2023-04-02  5:24               ` Eli Zaretskii
2023-04-05  7:30               ` Philip Kaludercic
2023-04-06  3:52                 ` Okamsn
2023-04-06 15:42                   ` Philip Kaludercic
2023-04-10 13:39                     ` Philip Kaludercic
2023-04-12  0:04                       ` Okamsn
2023-04-12  7:27                         ` Philip Kaludercic
2023-04-12  7:41                           ` Eli Zaretskii [this message]
2023-04-12  7:48                             ` Philip Kaludercic
2023-04-07 21:46             ` Jonas Bernoulli
2023-04-08  8:36               ` Philip Kaludercic
2023-04-09 18:39                 ` Jonas Bernoulli
2023-04-09 20:44                   ` Lynn Winebarger
2023-04-09 21:55                   ` Philip Kaludercic
2023-03-28 11:48           ` Eli Zaretskii

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=837cuh8s4a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=okamsn@protonmail.com \
    --cc=philipk@posteo.net \
    /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).