From: Glenn Morris <rgm@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: bug-gnu-emacs@gnu.org, rms@gnu.org
Subject: Re: Info-history is not in the Info manual
Date: Sat, 29 Sep 2007 19:03:17 -0400 [thread overview]
Message-ID: <uahcld13d6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 874phd5cf3.fsf@jurta.org
Juri Linkov wrote:
> I documented it in Emacs-22. I'm not sure if it will propagate to
> the trunk or not after the recent changes of the doc directory
> layout.
The 22 -> trunk merging happens via arch, and the arch tags in the
files enable arch to cope with moved files. So there should be no
problem. Although no merging of any kind has happened for a while.
prev parent reply other threads:[~2007-09-29 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 8:51 Info-history is not in the Info manual Drew Adams
2007-09-24 0:54 ` Juri Linkov
2007-09-24 1:21 ` Drew Adams
2007-09-24 18:20 ` Richard Stallman
2007-09-29 22:35 ` Juri Linkov
2007-09-29 23:03 ` Glenn Morris [this message]
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=uahcld13d6.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
/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).