all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Glenn Morris" <rgm@gnu.org>, <emacs-devel@gnu.org>
Subject: RE: merge emacs-pretest-bug and emacs-devel
Date: Thu, 9 Aug 2007 08:46:26 -0700	[thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACKEFGCBAA.drew.adams@oracle.com> (raw)
In-Reply-To: <9psl6tmpzo.fsf@fencepost.gnu.org>

> This has come up before at least once...
> Given the way the pretest-bug list is being used, there is little
> point having it. Indeed, it often causes extra work, with discussions
> split on two lists.
>
> When making emacs-pretest-bug an alias for emacs-devel was proposed in
> March those who replied were in favour, but it never happened:
>
> http://lists.gnu.org/archive/html/emacs-devel/2007-03/msg00344.html
>   From:     Richard Stallman
>   Subject:  Emacs pretest bug reports
>   Date:     Tue, 06 Mar 2007 17:36:33 -0500

Not everyone who replied was in favor.  I, for one, am not.

I would prefer to separate most bug discussions from the rest of emacs-devel
discussion. If there were a merge to be made, I would prefer that it be
emacs-pretest with bug-gnu-emacs - but perhaps that could lead to confusion.

I might be a minority of one on this, however. You are right that most
people in the previous discussion were in favor of merging emacs-pretest
with emacs-devel.

  reply	other threads:[~2007-08-09 15:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  1:54 merge emacs-pretest-bug and emacs-devel Glenn Morris
2007-08-09 15:46 ` Drew Adams [this message]
2007-08-09 21:04   ` Nick Roberts
2007-08-09 21:15     ` Drew Adams
2007-08-11  5:05       ` Richard Stallman
2007-08-12  3:23         ` Glenn Morris
2007-08-12  4:57           ` Drew Adams
2007-08-13  7:57             ` Glenn Morris
2007-08-13 14:16               ` Drew Adams
2007-08-12 17:56           ` Richard Stallman
2007-08-13  7:40             ` Glenn Morris
2007-08-12 18:51           ` Eli Zaretskii
2007-08-13  7:39             ` Glenn Morris
2007-08-13 19:45               ` Eli Zaretskii
2007-08-14  7:54                 ` Glenn Morris
2007-08-14 23:26                   ` Richard Stallman
2007-08-14 23:36                     ` David Kastrup
2007-08-15 11:11                       ` Juri Linkov
2007-08-15 11:25                         ` David Kastrup
2007-08-15 18:22                       ` Richard Stallman
2007-08-13 14:41           ` Ken Manheimer
2007-08-13 17:12           ` Reiner Steib
2007-08-14 16:06             ` Richard Stallman
2007-08-14 19:26               ` Michaël Cadilhac
2007-08-15  2:24                 ` Michaël Cadilhac
2007-08-15  6:27                   ` Reiner Steib
2007-08-15 11:18                     ` Michaël Cadilhac
2007-08-17  9:12                       ` Michaël Cadilhac
2007-08-17 11:20                         ` Eli Zaretskii
2007-08-17 11:41                           ` Michaël Cadilhac
2007-08-17 12:37                             ` Eli Zaretskii
2007-08-17 12:55                               ` Michaël Cadilhac
2007-08-17 13:24                                 ` Eli Zaretskii
2007-08-17 13:29                                   ` Michaël Cadilhac
2007-08-17 18:40                                     ` Eli Zaretskii

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=BNELLINCGFJLDJIKDGACKEFGCBAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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 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.