From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: savannah-hackers@gnu.org, emacs-devel@gnu.org
Subject: Re: Info about available CVS/Arch/Git branches
Date: Thu, 09 Aug 2007 22:57:25 +0200 [thread overview]
Message-ID: <v91wec8lze.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <jwvodhgk91q.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 09 Aug 2007 11:59:40 -0400")
On Thu, Aug 09 2007, Stefan Monnier wrote:
> CVS
> ---
> trunk : branch of the next major revision, to become 23.X.
> Bidirectionally sync'd with the Gnus stable branch.
While "Gnus stable branch" is true at the moment, our aim is to change
this to "Gnus trunk" soon.
I'm not sure if the information about Gnus is useful here in the first
place. At least this line is more important for most Emacs user an
should precede the info on Gnus:
> Changes from EMACS_22_BASE get auto-added here as well.
> EMACS_22_BASE: branch where we prepare the next minor revisions 22.X.
> emacs-unicode-2: branch where the inernel text representation has been
s/inernel/internal/?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-08-09 20:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 15:59 Info about available CVS/Arch/Git branches Stefan Monnier
2007-08-09 20:57 ` Reiner Steib [this message]
2007-08-12 3:45 ` Michael Olson
2007-08-12 9:10 ` Andreas Schwab
2007-08-13 9:42 ` David Kastrup
2007-08-13 10:06 ` Jim Meyering
2007-08-13 10:21 ` David Kastrup
2007-08-13 10:52 ` dhruva
2007-08-13 11:05 ` David Kastrup
2007-08-18 9:20 ` Andreas Schwab
2007-08-18 10:39 ` dhruva
2007-08-20 4:22 ` Miles Bader
2007-08-20 6:12 ` dhruva
2007-08-13 11:50 ` Jim Meyering
2007-08-13 13:05 ` Andreas Schwab
2007-08-13 13:07 ` Jim Meyering
2007-08-13 13:28 ` Randal L. Schwartz
2007-08-13 14:46 ` Jim Meyering
2007-08-13 16:41 ` Jim Meyering
2007-08-13 14:32 ` Andreas Schwab
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=v91wec8lze.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=savannah-hackers@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).