view admin/make-announcement @ 66518:7cc22b3f2300

* mh-comp.el (mh-annotate-msg): Use new variable mh-scan-field-destination-offset rather than hard-coding 1. * mh-customize.el (mh-interpret-number-as-range-flag): Add * to docstring. (mh-adaptive-cmd-note-flag-check, mh-scan-format-file-check): New functions to check input for mh-adaptive-cmd-note-flag and mh-scan-format-file respectively. (mh-adaptive-cmd-note-flag, mh-scan-format-file): Docstring fixes, add :set. * mh-e.el: (mh-scan-field-destination-offset): New variable. The destination is the -, t, b, c, or n character for Replied, To, cc, Bcc, or Newsgroups respectively. (mh-make-folder, mh-regenerate-headers, mh-generate-new-cmd-note) Call new function mh-msg-num-width-to-column to make leap between width and column more explicit. (mh-msg-num-width-to-column): New function that steals logic from old mh-set-cmd-note. Also, throw error if mh-scan-format-file isn't t since we can't adapt the scan lines in this case. (mh-set-cmd-note): Now just simply sets mh-cmd-note which will make the documentation more clear. (mh-generate-new-cmd-note): Docstring fix--mh-cmd-note is a column, not a width. (mh-add-sequence-notation, mh-remove-sequence-notation): Use new variable mh-scan-field-destination-offset rather than hard-coding 1. * mh-utils.el (mh-cmd-note) Synced docstring with manual. (mh-notate): Use new variable mh-scan-field-destination-offset rather than hard-coding 1. (mh-message-number-width): Rename to mh-msg-num-width to be consistent with mh-get-msg-num and mh-msg-num-width-to-column.
author Bill Wohler <wohler@newt.com>
date Sat, 29 Oct 2005 05:09:05 +0000
parents 695cf19ef79e
children 53c1af431f97 375f2633d815
line wrap: on
line source

#! /bin/bash

if [ $# -ne 2 ]; then
    echo "usage: $0 <old version number> <new version number>" >&2
    exit 1
fi

if [ ! -f INSTALL -o ! -f configure -o ! -d lib-src ]; then
    echo "this script should be run in the emacs root directory" >&2
    exit 2
fi

OLD=$1
NEW=$2
outfile=emacs-$NEW.announce
oldtag=EMACS_PRETEST_$(echo $OLD|tr . _)
newtag=EMACS_PRETEST_$(echo $NEW|tr . _)

if [ -f $outfile ]; then
    echo "$outfile exists"
    echo -n "interrupt to abort, ENTER to overwrite "; read answer
fi

echo -n "tag name for OLD emacs version $OLD [$oldtag]: "; read answer
if [ "$answer" ]; then oldtag=$answer; fi

echo -n "tag name for NEW emacs version $NEW [$newtag]: "; read answer
if [ "$answer" ]; then newtag=$answer; fi

exec > $outfile

cat <<EOF
There is a new pretest available in

  <ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-$NEW.tar.gz>
  <ftp://alpha.gnu.org/gnu/emacs/pretest/leim-$NEW.tar.gz>

Please report results from compiling and running the pretest to
<emacs-pretest-bug@gnu.org>.  Your feedback is necessary for us
to know on which platforms the pretest has been tried.
Please say whether you built with LEIM or not.

If you have the tars from the previous pretest, and you have the
\`xdelta' utility, you can instead download the much smaller

  <ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-$OLD-$NEW.xdelta>
  <ftp://alpha.gnu.org/gnu/emacs/pretest/leim-$OLD-$NEW.xdelta>

You can use a command like

  $ xdelta patch XDELTA PREVIOUS-TAR CURRENT-TAR

to generate the new tar from the old one, where XDELTA is the xdelta
file you downloaded, PREVIOUS-TAR is the tar file from the previous
pretest, and CURRENT-TAR is the name of the tar file you downloaded.

Information about xdelta can be found on the GNU ftp site, in
/non-gnu/xdelta.README.

Changes since $OLD

EOF

make-changelog-diff $oldtag $newtag

echo " announcement created in $outfile" >&2

# arch-tag: 605e00c7-7330-4c45-81e1-2ed53a13c39f