unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: can Gnus simply use the Emacs bug tracker?
Date: Wed, 16 Mar 2011 10:58:42 -0500	[thread overview]
Message-ID: <87vczjukel.fsf@lifelogs.com> (raw)
In-Reply-To: jwvhbb3nke3.fsf-monnier+emacs@gnu.org

On Wed, 16 Mar 2011 11:41:44 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>>>> There was a point where Gnus was merged into Emacs.  Do we want that to
>>>> be the separation point?  Or do we want all non-trunk reports to go to
>>>> Gnus only?  I'm not sure.

GM> IMO, if someone is using the version of Gnus that came with their Emacs,
GM> they should send bug reports to bug-gnu-emacs. If not, ie if they
GM> downloaded a separate version of Gnus, then to bugs@gnus.

>> Oh, that makes perfect sense.  So in the Gnus trunk we'll set 
>> `M-x gnus-bug' to send to bugs@gnus.org and insert "Package: gnus".  But
>> in the Emacs trunk the same command will send to bug-gnu-emacs and
>> insert "Package: emacs,gnus".  Is that correct?

SM> Sounds fine to me.
SM> I'm also OK with sending ll to bug-gnu-emacs (and maybe distinguishing
SM> the two by using either "gnus" or "emacs,gnus" as package).

Glenn, is Stefan's suggestion easier to implement (I would guess so)?

I'm OK with either approach as well.

Ted




  reply	other threads:[~2011-03-16 15:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 16:38 can Gnus simply use the Emacs bug tracker? Ted Zlatanov
2011-03-15 17:40 ` Chong Yidong
2011-03-15 18:27   ` Ted Zlatanov
2011-03-15 19:32   ` Glenn Morris
2011-03-15 19:08 ` Stefan Monnier
2011-03-15 19:23 ` Glenn Morris
2011-03-15 19:41   ` Lars Magne Ingebrigtsen
2011-03-15 19:47   ` Ted Zlatanov
2011-03-15 23:27     ` Glenn Morris
2011-03-16 14:00       ` Ted Zlatanov
2011-03-16 15:41         ` Stefan Monnier
2011-03-16 15:58           ` Ted Zlatanov [this message]
2011-03-16 17:51             ` Glenn Morris
2011-03-16 17:55               ` Glenn Morris
2011-03-16 19:41                 ` Stefan Monnier
2011-03-16 17:32         ` Lars Magne Ingebrigtsen
2011-03-16 18:44           ` Ted Zlatanov
2011-03-17 16:52             ` Lars Magne Ingebrigtsen
2011-03-17 17:27               ` Ted Zlatanov
2011-03-17 17:40                 ` Lars Magne Ingebrigtsen
2011-03-17 17:50                   ` Glenn Morris
2011-03-17 17:53                     ` Glenn Morris
2011-03-18  8:33                     ` Reiner Steib
2011-03-18 13:04                       ` Ted Zlatanov
2011-03-29 18:53                         ` Lars Magne Ingebrigtsen
2011-03-29 19:09                           ` Ted Zlatanov
2011-06-28 15:31                           ` Ted Zlatanov
2011-03-17 19:12                   ` Ted Zlatanov
2011-06-28 15:33                   ` Ted Zlatanov
2011-03-15 20:31   ` Chong Yidong
2011-03-15 20:45     ` Lars Magne Ingebrigtsen

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=87vczjukel.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).