From: Sebastian Freundt <hroptatyr@sxemacs.org>
Subject: Re: Gnus interface to Bugzilla?
Date: Thu, 13 Apr 2006 16:25:48 +0000 [thread overview]
Message-ID: <nht7j5tigs3.fsf@muck.math.tu-berlin.de> (raw)
In-Reply-To: <8764ldbglq.fsf@pacem.orebokech.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Romain Francoise <romain@orebokech.com> writes:
> The one-group-per-bug approach is better and doesn't conflict with
> one-group-per-product: you can just gather all bugs for one product into
> one group with nnvirtual.
>
> (That's how I solve the one-group-per-month vs. one-group-per-year
> problem for mail archives: outgoing messages go into per-month groups,
> and I gather them into several per-year nnvirtual groups, and one global
> nnvirtual group.)
What's the regexp to gather them? For nnarchive groups based on a
date-stamp this is obvious to me. But what, like Lars suggest, groups look
like:
nnbugzilla:Again problems with this bugzilla backend
Sebastian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEPnuTlMmhrILJOQ4RAnJXAKCCqtUd9vElWKbzyW898k/9EM1wTACaA8d+
Omx5RuxWKtygKf9runmoEgQ=
=XQ5z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-04-13 16:25 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 [this message]
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
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=nht7j5tigs3.fsf@muck.math.tu-berlin.de \
--to=hroptatyr@sxemacs.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).