From: Dan Hoey <Hoey@aic.nrl.navy.mil>
Subject: Re: What shall we do to verify the CVS diffs for emacs?
Date: Tue, 13 Jan 2004 16:34:25 -0500 (EST) [thread overview]
Message-ID: <200401132134.i0DLYPO2006888@sun1.aic.nrl.navy.mil> (raw)
On 16 Dec 2003 02:29:46 +0100, Kim F. Storm wrote:
> Emacs diffs are now ready for verification.
> See http://savannah.gnu.org/statement.html
> How shall we organize the verification of those diffs?
On 16 Dec 2003 22:27:47 -0500, Richard Stallman wrote:
> It would be very useful for someone to take overall charge of the
> verification activity--to make sure that at least the important files
> do get checked. I can't do it myself, though; I don't have time.
> (Since my elbow broke, I have barely been able to work on Emacs at
> all.)
> Can someone volunteer to do this?
Was anything done about this? Is it going to be left to luck that
anything bogus will eventually be noticed? I'm not complaining (or
volunteering), but I'd like to know if there is any peace-of-mind
increment on the horizon.
Dan
Hoey@AIC.NRL.Navy.Mil
next reply other threads:[~2004-01-13 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 21:34 Dan Hoey [this message]
2004-01-14 6:14 ` What shall we do to verify the CVS diffs for emacs? Eli Zaretskii
2004-01-14 20:08 ` Dan Hoey
2004-01-15 11:43 ` Thien-Thi Nguyen
2004-01-15 18:47 ` David Kastrup
2004-01-15 20:32 ` Thien-Thi Nguyen
2004-01-15 21:21 ` Richard Stallman
2004-01-16 2:11 ` Kim F. Storm
2004-01-16 19:54 ` Richard Stallman
2004-01-16 23:04 ` Miles Bader
2004-01-17 1:55 ` Kim F. Storm
2004-01-17 1:27 ` Miles Bader
2004-01-17 12:54 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 1:29 Kim F. Storm
2003-12-17 3:27 ` 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=200401132134.i0DLYPO2006888@sun1.aic.nrl.navy.mil \
--to=hoey@aic.nrl.navy.mil \
/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).