From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, Karl Berry <karl@freefriends.org>,
emacs-devel@gnu.org
Subject: Re: info.el
Date: Thu, 08 Apr 2004 17:57:39 +0200 [thread overview]
Message-ID: <87k70q5uoc.fsf@peder.flower> (raw)
In-Reply-To: <87zn9mfpge.fsf-monnier+emacs@alfajor.local> (Stefan Monnier's message of "08 Apr 2004 11:40:38 -0400")
Stefan Monnier writes:
>> what is the the 22.0/21.4 RC branch called, I never could seem to
>> find id.
>
> It's not called: it's the trunk.
Hmm. That explains I could not find it, but confuses me even more.
How to interpret Juri's comment:
installing it on the RC branch is not needed if HEAD will be
merged into RC branch
HEAD is to be merged into trunk?
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
next prev parent reply other threads:[~2004-04-08 15:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 9:44 info.el Juri Linkov
2004-04-06 0:20 ` info.el Karl Berry
2004-04-06 4:05 ` info.el Juri Linkov
2004-04-06 12:51 ` info.el Jan Nieuwenhuizen
2004-04-06 13:17 ` info.el Karl Berry
2004-04-08 4:05 ` info.el Juri Linkov
2004-04-08 12:44 ` info.el Jan Nieuwenhuizen
2004-04-08 15:40 ` info.el Stefan Monnier
2004-04-08 15:57 ` Jan Nieuwenhuizen [this message]
2004-04-08 17:21 ` info.el Stefan Monnier
2004-04-08 16:01 ` info.el Karl Berry
-- strict thread matches above, loose matches on Subject: below --
2004-04-11 17:20 info.el Luc Teirlinck
2004-04-11 17:26 ` info.el Luc Teirlinck
2004-04-12 5:06 ` info.el Juri Linkov
2005-08-04 0:29 info.el Juri Linkov
2005-08-04 20:46 ` info.el Richard M. Stallman
2005-08-05 0:05 ` info.el Juri Linkov
2005-08-05 4:31 ` info.el Luc Teirlinck
2005-08-05 5:02 ` info.el Juri Linkov
2005-08-05 4:45 ` info.el Luc Teirlinck
2005-08-05 20:37 ` info.el Richard M. Stallman
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=87k70q5uoc.fsf@peder.flower \
--to=janneke@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=karl@freefriends.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 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.