unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: emacs-unicode@gnu.org
Cc: emacs-devel@gnu.org
Subject: adding warning to obsolete unicode branch
Date: Mon, 04 Feb 2008 03:57:19 +0900	[thread overview]
Message-ID: <87myqhj2b4.fsf@catnip.gol.com> (raw)

As a large number of people used the emacs-unicode-2 branch
out of CVS, I think it might be a good idea to add a warning
to the configure script and Makefiles in the branch, so that
if they update from that branch and build emacs, they'll get
a big fat message telling them they should probably use the
trunk instead.

E.g.

********************************************************************
**                                                                **
**  The Emacs "emacs-unicode-2" branch has been merged into       **
**  the CVS trunk, and is now obsolete.  You should probably      **
**  use the CVS trunk instead.                                    **
**                                                                **
**  To switch a CVS checkout to the trunk, use the command:       **
**                                                                **
**     cvs update -A                                              **
**                                                                **
********************************************************************

The configure script is easy, though I'm not exactly sure
which make targets such a thing should be added to...

Any opinions?

Thanks,

-Miles

-- 
`To alcohol!  The cause of, and solution to,
 all of life's problems' --Homer J. Simpson




             reply	other threads:[~2008-02-03 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 18:57 Miles Bader [this message]
2008-02-03 19:35 ` adding warning to obsolete unicode branch Dan Nicolaescu
2008-02-03 20:45 ` Sean Sieger
2008-02-04  2:40 ` Richard Stallman
2008-02-17 16:17 ` David Abrahams
2008-02-17 19:47   ` Miles Bader

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=87myqhj2b4.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-unicode@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).