unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: esr@thyrsus.com (Eric S. Raymond)
Cc: emacs-devel@gnu.org
Subject: Re: Should 'old-branches' and 'other-branches' be kept?
Date: Tue, 11 Feb 2014 20:53:22 -0500	[thread overview]
Message-ID: <jwvtxc5umi7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20140211203302.67959380834@snark.thyrsus.com> (Eric S. Raymond's message of "Tue, 11 Feb 2014 15:33:02 -0500 (EST)")

> 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?

http://bzr.savannah.gnu.org/r/emacs/README says:

   [...]
   `old-branches' Directory of branches that have been merged into trunk already.
   `other-branches' Directory of various other branches.
   [...]

I don't see any point in getting rid of them, tho.


        Stefan



  reply	other threads:[~2014-02-12  1:53 UTC|newest]

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

  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=jwvtxc5umi7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.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.
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).