From: Tim Goodwin <email@example.com> To: firstname.lastname@example.org Subject: Beta release rc-1.5b6 Date: Thu, 13 May 1999 11:09:18 -0400 [thread overview] Message-ID: <xS8AAB7rOjePbwsA@ltsun0.star.le.ac.uk> (raw) A new beta release of rc is available, rc-1.5b6. Details of changes since rc-1.5b5 are below. There are no known outstanding problems with this beta. Unless anybody can give me a reason not to, I will make the full release of rc-1.6 in a week or two's time. So this is your last chance to test rc before a major release (I'd particularly appreciate confirmation that the configure script now finds tgetent() in -lncurses on Debian Linux). You can obtain rc from here. http://www.star.le.ac.uk/~tjg/rc/beta/rc-1.5b6.tar.gz If you don't have gzip handy, remove the `.gz' for an uncompressed tarball. If you are unable to use HTTP to obtain rc, please contact me and we'll figure out some way to get it to you. Thanks to all the people who have contributed to this release, by suggesting ideas, contributing code, or giving feedback on earlier releases. Tim. 1999-02-15 Portability: AM_INIT_AUTOMAKE calls AC_ARG_PROGRAM and AC_PROG_INSTALL. Don't do it explicitly. For once, the configure script gets smaller! Program name transformations work right now. Documentation: note that rc has no `set' builtin; fix weird variable name example; any character except `=' may be used in a variable name; document bqstatus; document rc's exit status; other tidying. 1999-03-01 Documentation: document the yacc-imposed limit on ; separated commands in a line. 1999-05-06 Portability: tgetent() might be in -lncurses instead of -ltermcap. 1999-05-10 Portability: Linux *almost* has SysV SIGCLD semantics, and we need to detect them. Bug: if we reset SIGCLD to SIG_DFL, we need to record the fact in the sighandlers array. 1999-05-12 Documentation: note that `$(a.b)' syntax only mostly works, and that list definitions in exported functions are noisier than they need to be. Release: rc-1.5b6.
reply other threads:[~1999-05-13 21:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xS8AAB7rOjePbwsA@ltsun0.star.le.ac.uk \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Beta release rc-1.5b6' \ /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
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 NNTP newsgroup(s).