all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Hoey <Hoey@aic.nrl.navy.mil>
Subject: Re: What shall we do to verify the CVS diffs for emacs?
Date: Wed, 14 Jan 2004 15:08:24 -0500 (EST)	[thread overview]
Message-ID: <200401142008.i0EK8OUI007731@sun1.aic.nrl.navy.mil> (raw)
In-Reply-To: <uwu7voy4d.fsf@elta.co.il>

Eli Zaretskii <eliz@elta.co.il> wrote:

> > Was anything done about this?

> Not that I know of.

> > Is it going to be left to luck that anything bogus will eventually
> > be noticed?

> Probably.  It's free software maintained by a bunch of volunteers on
> their free time, so unless you are willing to volunteer, there's no
> sense in nagging.

I tried to make it clear that I am not nagging.  That's why I wrote

> > I'm not complaining (or volunteering), but I'd like to know if
> > there is any peace-of-mind increment on the horizon.

I'm just trying to find out what the situation is--e.g., whether there
is some off-list work being done.  Thank you for your assessment of
the situation.  If anyone has further information, I'd be most
grateful to hear about it.

Dan

  reply	other threads:[~2004-01-14 20:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 21:34 What shall we do to verify the CVS diffs for emacs? Dan Hoey
2004-01-14  6:14 ` Eli Zaretskii
2004-01-14 20:08   ` Dan Hoey [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200401142008.i0EK8OUI007731@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.