all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: esr@thyrsus.com (Eric S. Raymond)
To: emacs-devel@gnu.org
Subject: Should 'old-branches' and 'other-branches' be kept?
Date: Tue, 11 Feb 2014 15:33:02 -0500 (EST)	[thread overview]
Message-ID: <20140211203302.67959380834@snark.thyrsus.com> (raw)

I'm looking at the old0branches and other-branches remote groups.  It
seems pretty clear that most of these were either marged to trunk or
abandoned during the CVS period.  Are any of them worth keeping
around?

old-branches/EMACS_21_1_RC
old-branches/EMACS_22_BASE
old-branches/EMACS_23_1_RC
old-branches/NewVC-fileset
old-branches/branch-5_8
old-branches/cedet-branch
old-branches/elpa
old-branches/emacs-unicode
old-branches/emacs-unicode-2
old-branches/font-backend
old-branches/gerd_defvaralias
old-branches/gnus-5_10-branch
old-branches/imagemagick
old-branches/lexbind
old-branches/lexbind-new
old-branches/multi-tty
old-branches/pending
old-branches/profiler
old-branches/python
old-branches/rmail-mbox-branch
old-branches/unicode-xft
old-branches/window-pub
other-branches/Boehm-GC
other-branches/Boehm-versions
other-branches/DAVELOVE
other-branches/FLYSPELL
other-branches/ILYA
other-branches/URL
other-branches/VENDOR
other-branches/XFT_JHD_BRANCH
other-branches/custom_themes
other-branches/fx-branch
other-branches/gerd_0001
other-branches/gerd_big
other-branches/gerd_dbe
other-branches/gerd_int
other-branches/glibc-2_0_x
other-branches/master-UNNAMED-BRANCH
other-branches/miles-orphaned-changes
other-branches/old-bidi
other-branches/old-concurrency
other-branches/patches_21_0
other-branches/test2
other-branches/thomas-posix1996
other-branches/ttn-vms-21-2-stash
other-branches/ttn-vms-21-3-stash

--
				>>esr>>



             reply	other threads:[~2014-02-11 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 20:33 Eric S. Raymond [this message]
2014-02-12  1:53 ` Should 'old-branches' and 'other-branches' be kept? Stefan Monnier
2014-02-12  3:23   ` Eric S. Raymond
2014-02-12 14:01     ` Stefan Monnier
2014-02-12 14:30       ` Eric S. Raymond

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140211203302.67959380834@snark.thyrsus.com \
    --to=esr@thyrsus.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.