From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Release schedule for 22.2
Date: Sat, 22 Mar 2008 16:38:20 -0700 [thread overview]
Message-ID: <200803222338.m2MNcKmo015637@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <87abkq318m.fsf@stupidchicken.com> (Chong Yidong's message of "Sat, 22 Mar 2008 17:19:53 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > Chong Yidong <cyd@stupidchicken.com> writes:
> >
> > > If nothing goes wrong, I plan to roll the 22.2 tarball next Wednesday,
> > > the 26th of March. If you have any fixes that you would like to add
> > > to the branch, please inform emacs-devel ASAP.
> >
> > I received theses 2 patches for verilog-mode.el. Should they go in 22.2 ?
> >
> > 2008-03-17 Wilson Snyder <wsnyder@wsnyder.org>
> >
> > * progmodes/verilog-mode.el (verilog-easy-menu-filter):
> > Add menu tool tip :helps and filter appropriately.
> >
> > * verilog-mode.el (verilog-customize) (verilog-font-customize)
> > (electric-verilog-backward-sexp) (electric-verilog-forward-sexp)
> > (verilog-mode): Update documentation strings to match tool tips.
>
> These can wait till after the release.
Stefan OKed them a few days ago, so they are already checked in. Should
I take them out?
next prev parent reply other threads:[~2008-03-22 23:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 20:02 Release schedule for 22.2 Chong Yidong
2008-03-18 22:39 ` Reiner Steib
2008-03-18 23:18 ` Chong Yidong
2008-03-19 9:57 ` Reiner Steib
2008-03-19 17:55 ` Chong Yidong
2008-03-18 23:31 ` Glenn Morris
2008-03-19 9:33 ` Reiner Steib
2008-03-19 4:03 ` Dan Nicolaescu
2008-03-19 9:37 ` (eval-and-compile (featurep 'xemacs))? (was: Release schedule for 22.2) Reiner Steib
2008-03-19 14:33 ` Release schedule for 22.2 Stefan Monnier
2008-03-22 21:19 ` Chong Yidong
2008-03-22 23:38 ` Dan Nicolaescu [this message]
2008-03-23 13:45 ` Chong Yidong
2008-03-25 13:26 ` Chong Yidong
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=200803222338.m2MNcKmo015637@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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).