unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: michael@cadilhac.name (Michaël Cadilhac)
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: When can we pretest Emacs 22.2?
Date: Sun, 26 Aug 2007 12:01:16 +0200	[thread overview]
Message-ID: <871wdqr4wj.fsf@cadilhac.name> (raw)
In-Reply-To: <E1IP6c3-00044Q-PP@fencepost.gnu.org> (Richard Stallman's message of "Sat, 25 Aug 2007 21:08:23 -0400")


[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]

Richard Stallman <rms@gnu.org> writes:

>     I think it would be asier to keep track of what needs to be done if
>     you reverted to the method of putting entries in FOR-RELEASE, rather
>     than sending emails. But perhaps that would be more work for you.
>
> I can start putting them into FOR-RELEASE sooner, if that will help
> encourage people to fix bugs.

In my case, it will.  I only read the mailing list sporadically, so a
summary of all the pending bugs would be really great.  My spare time
would be focused on finding a solution to a bug, not finding a bug :-)

-- 
 |   Michaël `Micha' Cadilhac       |  In a World without Walls and Fences,  |
 |   http://michael.cadilhac.name   |     who needs Windows and Gates?       |
 |   JID/MSN:                       |          -- Dino Esposito              |
 `----  michael.cadilhac@gmail.com  |                                   -  --'

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

      parent reply	other threads:[~2007-08-26 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 16:10 When can we pretest Emacs 22.2? Richard Stallman
2007-08-25 19:15 ` Glenn Morris
2007-08-26  1:08   ` Richard Stallman
2007-08-26  2:03     ` Glenn Morris
2007-08-26 10:01     ` Michaël Cadilhac [this message]

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=871wdqr4wj.fsf@cadilhac.name \
    --to=michael@cadilhac.name \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).