unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alan Mackenzie<none@example.invalid>
Subject: On Savannah:  What are "arch" and "bidi" and ....
Date: Fri, 7 May 2004 08:11:01 +0000	[thread overview]
Message-ID: <lagf7c.q5.ln@acm.acm> (raw)

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.

I mean, one would have thought that the arch branch was a part of tree,
sweeping elegantly upwards from low down on the trunk, perhaps covering a
neighbouring path with luscious leaves, sheltering from the rain those
standing under it.

And I always thought a bidi was a low sink one sat in to, well, wash
something or other in.

Is "arch" short for "architecture" or "archive" or something else?

"RC" is often used to identify a large and powerful Christian sect.

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?

Thanks in advance for the answers!

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").

             reply	other threads:[~2004-05-07  8:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  8:11 Alan Mackenzie [this message]
2004-05-07 15:19 ` On Savannah: What are "arch" and "bidi" and Gernot Hassenpflug
2004-05-07 21:58   ` Miles Bader
2004-05-07 16:07 ` Kevin Rodgers
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=lagf7c.q5.ln@acm.acm \
    --to=none@example.invalid \
    /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).