From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: emacs-unicode@gnu.org, emacs-devel@gnu.org
Subject: Re: adding warning to obsolete unicode branch
Date: Sun, 03 Feb 2008 11:35:43 -0800 [thread overview]
Message-ID: <200802031935.m13JZvKD019404@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <87myqhj2b4.fsf@catnip.gol.com> (Miles Bader's message of "Mon, 04 Feb 2008 03:57:19 +0900")
Miles Bader <miles@gnu.org> writes:
> 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?
How about just make configure exit after printing the message above,
that way there's no need worry about the makefiles.
next prev parent reply other threads:[~2008-02-03 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 18:57 adding warning to obsolete unicode branch Miles Bader
2008-02-03 19:35 ` Dan Nicolaescu [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802031935.m13JZvKD019404@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=emacs-unicode@gnu.org \
--cc=miles@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.