From: Chong Yidong <cyd@stupidchicken.com>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: What is holding the release?
Date: Sat, 31 Mar 2007 12:10:47 -0400 [thread overview]
Message-ID: <87lkhd4cmw.fsf@stupidchicken.com> (raw)
In-Reply-To: <f7ccd24b0703310414p3647dc71qc5013769df6cf944@mail.gmail.com> (Juanma Barranquero's message of "Sat\, 31 Mar 2007 13\:14\:20 +0200")
"Juanma Barranquero" <lekktu@gmail.com> writes:
> On 3/31/07, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> If not, let's fix the single remaining
>> problem (what is it, btw?)
>
> http://article.gmane.org/gmane.emacs.pretest.bugs/17862
I've proposed a fix for this.
next prev parent reply other threads:[~2007-03-31 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 8:54 What is holding the release? Eli Zaretskii
2007-03-31 11:14 ` Juanma Barranquero
2007-03-31 16:10 ` Chong Yidong [this message]
2007-03-31 23:20 ` Richard Stallman
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=87lkhd4cmw.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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).