unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Miles Bader" <miles@gnu.org>
To: "David Kastrup" <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Other branches? (was: emacs-unicode-2 branch)
Date: Mon, 19 Mar 2007 10:40:53 +0900	[thread overview]
Message-ID: <fc339e4a0703181840hec9952fga8e86014bb7235e9@mail.gmail.com> (raw)
In-Reply-To: <85abyav6wl.fsf@lola.goethe.zz>

On 3/19/07, David Kastrup <dak@gnu.org> wrote:
> Can we assume that no other branches were affected apaprt from
> emacs-unicode-2 and head?
...
> After all, we have a number of semi-active branches like emacs-xft (or
> something like that), emacs-bidi, emacs-multitty, even
> emacs-lexical-something.
>
> At least for the post-catch 22 branches (maybe xft, more certainly
> multitty), it would be somewhat nice to know we have not lost them.

[Is multi-tty in the emacs repository now?  It used to be external...]

I think most of the branches are not very active at all, and there's
usually one person that mostly commits to them, so we can just rely on
that person to check.  The "xft" branch is almost defunct I think, and
as far as I know I'm the only person who's committed to it in ages.
The "lexical" branch is also mine, so I can verify that.

[Of course one more general way would be for someone to use the
rsync'd version of the repository to check out copies of the
semi-active branches, and check that they're equal to what's in the
official repository.  I'm not going to do that though...]

-Miles

-- 
Do not taunt Happy Fun Ball.

  reply	other threads:[~2007-03-19  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18 16:27 emacs-unicode-2 branch Miles Bader
2007-03-18 16:43 ` Other branches? (was: emacs-unicode-2 branch) David Kastrup
2007-03-19  1:40   ` Miles Bader [this message]
2007-03-19  2:43 ` emacs-unicode-2 branch Kenichi Handa

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=fc339e4a0703181840hec9952fga8e86014bb7235e9@mail.gmail.com \
    --to=miles@gnu.org \
    --cc=dak@gnu.org \
    --cc=emacs-devel@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).