unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: On Savannah:  What are "arch" and "bidi" and ....
Date: Fri, 07 May 2004 10:07:38 -0600	[thread overview]
Message-ID: <409BB44A.1080107@yahoo.com> (raw)
In-Reply-To: lagf7c.q5.ln@acm.acm

Alan Mackenzie wrote:
 > At the risk of appearing stupid, would somebody please tell me the
 > purpose of the various named branches in the Emacs CVS repository.  I've
 > been seeing these names bandied about on the emacs-devel mailing list for
 > months, and haven't had the courage to ask before now.

You should ask on the emacs-devel mailing list then.

...

 > So, what are the "arch", "bidi", "lexical", "multi-tty", "RC", (Miles's)
 > "tiling", "Unicode" branches for?  Is there anywhere on savannah I could
 > have looked to find the answer myself?

arch is a new version control system, aka tla.  I don't understand the
relationship between CVS and arch, though.

bidi is the branch that supports bidirectional text, i.e. right-to-left
languages as well as left-to-right.

lexical is the branch that implements Emacs Lisp with lexical
(vs. dynamic) binding.

multi-tty is the branch that supports, uh, multiple ttys (for a single
emacs instance).

tiling is the branch that implements some fancy image features, like
background images.

unicode is obviously the branch that (fully) support Unicode -- it might
even use it as the internal encoding.

-- 
Kevin Rodgers

  parent reply	other threads:[~2004-05-07 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  8:11 On Savannah: What are "arch" and "bidi" and Alan Mackenzie
2004-05-07 15:19 ` Gernot Hassenpflug
2004-05-07 21:58   ` Miles Bader
2004-05-07 16:07 ` Kevin Rodgers [this message]
2004-05-07 22:03   ` Miles Bader
2004-05-09 19:35   ` Stefan Monnier
2004-05-07 16:31 ` Eli Zaretskii
     [not found] ` <mailman.3915.1083945524.1061.help-gnu-emacs@gnu.org>
2004-05-07 17:47   ` Alan Mackenzie

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=409BB44A.1080107@yahoo.com \
    --to=ihs_4664@yahoo.com \
    /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.
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).