savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-help-public] Info about available CVS/Arch/Git branches


From: Stefan Monnier
Subject: [Savannah-help-public] Info about available CVS/Arch/Git branches
Date: Thu, 09 Aug 2007 11:59:40 -0400
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux)

We'd like to add to http://savannah.gnu.org/projects/emacs
some info about the available/relevant branches in the CVS and
Arch repositories.  Basically something like

  CVS
  ---
    trunk : branch of the next major revision, to become 23.X.
            Bidirectionally sync'd with the Gnus stable branch.
            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
                     changed to be based on utf-8.  Slated to be merged into
                     the trunk before 23.1.
                     Changes from the trunk get auto-added here as well.
    multi-tty: branch where we added support for multi-ttys (via emacsclient).
               Slated to be merged into the trunk before 23.1
               Changes from the trunk get auto-added here as well.
    emacs-bidi: branch for development of bidirectional support.
                Very preliminary.

  Arch
  ----
    emacs--devo--0: bidirectionally sync'd with CVS's trunk.
    emacs--unicode--0: bidirectionally sync'd with CVS's emacs-unicode-2.
    emacs--multi-tty--0: bidirectionally sync'd with CVS's multi-tty.
    emacs--lexbind--0: branch where we add support for lexical scoping.


I could see this kind of info added directly to
http://savannah.gnu.org/cvs/?group=emacs or a separate page (in which case
it'd make sense to have a single page for all backends rather than one per
backend).

It could be structured (with fileds like "branch name", "branch status",
"description", "slated for merge into", "parent branch", "sync'd with", ...)
or be just plain text.


        Stefan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]