Gnus development mailing list
 help / color / mirror / Atom feed
From: Nelson Ferreira <nelson.ferreira@ieee.org>
Subject: Re: Gnus interface to Bugzilla?
Date: Thu, 13 Apr 2006 13:51:18 -0400	[thread overview]
Message-ID: <m3y7y9gy95.fsf@tuxie.homelinux.net> (raw)
In-Reply-To: <m364ldoam6.fsf@quimbies.gnus.org>

"Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

    Lars> Steve Youngs <steve@sxemacs.org> writes:
    >> No, that'd suck.  Each bug should be a thread within the group that is
    >> the "product".  We have 2 "products" in our Bugzilla, so you'd have
    >> something like...

    Lars> Hm...  the problem then would be things like "I want to see all the
    Lars> messages in bug #542, but not any others in the same product
    Lars> category".  With the one-group-per-bug approach, that would be `C-u
    Lars> RET', while with the one-group-per-product, it would require a
    Lars> separate special command.  And if you're not interested in a bug, you
    Lars> just kill the group.  Etc.

Why not 'overload' the concept of digest, i.e. treat the bug as a
digest and C-d would give you the replies there? If message-ids are
generated the read messages should still be marked as such right ?

    Lars> Of course, it helps if you use topics and all the new bugzilla groups
    Lars> end up there automatically.

I am not too fond of having groups created automatically, even with topics.


[...]


-- 
Nelson Ferreira




  parent reply	other threads:[~2006-04-13 17:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13  8:47 Lars Magne Ingebrigtsen
2006-04-13 11:45 ` Lars Magne Ingebrigtsen
2006-04-13 12:43 ` Steve Youngs
2006-04-13 13:42   ` Lars Magne Ingebrigtsen
2006-04-13 14:20     ` Steve Youngs
2006-04-13 14:27       ` Lars Magne Ingebrigtsen
2006-04-13 14:58         ` Sebastian Freundt
2006-04-13 16:11           ` Lars Magne Ingebrigtsen
2006-04-13 14:28       ` Lars Magne Ingebrigtsen
2006-04-13 16:11       ` Romain Francoise
2006-04-13 16:25         ` Sebastian Freundt
2006-04-13 16:42           ` Lars Magne Ingebrigtsen
2006-04-13 16:44           ` Romain Francoise
2006-04-13 16:56     ` Lars Magne Ingebrigtsen
2006-05-17 19:36       ` Steinar Bang
2006-04-13 17:51     ` Nelson Ferreira [this message]
2006-04-14  6:14       ` Lars Magne Ingebrigtsen
2006-04-14  7:21         ` Nelson Ferreira
2006-04-14  7:41           ` Lars Magne Ingebrigtsen
2006-04-13 16:20 ` Wes Hardaker
2006-04-13 16:36   ` Lars Magne Ingebrigtsen
2006-04-13 17:02     ` Lars Magne Ingebrigtsen
2006-04-13 17:29       ` Steve Youngs
2006-04-13 17:36         ` Lars Magne Ingebrigtsen
2006-04-13 18:27           ` Steve Youngs
2006-04-13 18:52             ` Lars Magne Ingebrigtsen
2006-04-13 17:50       ` Lars Magne Ingebrigtsen
2006-04-13 18:24         ` Steve Youngs
2006-04-13 17:04     ` Steve Youngs
2006-04-13 21:50     ` Wes Hardaker
2006-04-13 18:44 ` Romain Francoise
2006-04-14  6:03   ` Lars Magne Ingebrigtsen
2006-04-14  6:23     ` Romain Francoise
2006-04-14  6:38       ` Lars Magne Ingebrigtsen
2006-05-17 19:42         ` Steinar Bang

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=m3y7y9gy95.fsf@tuxie.homelinux.net \
    --to=nelson.ferreira@ieee.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.
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 NNTP newsgroup(s).