From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] January 2010 meeting date
Date: Mon, 21 Dec 2009 13:22:09 +0100 [thread overview]
Message-ID: <20091221122209.GB3308@gentoo.org> (raw)
In-Reply-To: <4B2F5C4F.2030001@gentoo.org>
On 21-12-2009 06:30:23 -0500, Richard Freeman wrote:
> On 12/21/2009 02:54 AM, Fabian Groffen wrote:
> > If all mail that would go to -dev-announce would guaranteed be sent to
> > -dev as well, I didn't have to check -dev-announce, and archives.g.o
> > would also have the original "January 2010 meeting date" mail in the
> > thread on -dev.
>
> Or you could just subscribe to both and add this to your procmailrc:
>
> :0 Wh: msgid.lock
> | formail -D 8192 msgid.cache
>
> :0 a:
> .duplicates/new
Does that fix archives.g.o? No.
> Cross-posting in general tends to mess up threads, but there isn't much
> that can be done about that unless we just ban it. However, most
> cross-posts are honest attempts to try to move list discussion to a
> place where it might better belong.
For commits I can imagine, but for this, it's just pointless.
--
Fabian Groffen
Gentoo on a different level
prev parent reply other threads:[~2009-12-21 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c612fc60912150854k608270cag61c533542075f5bf@mail.gmail.com>
2009-12-20 13:53 ` [gentoo-dev] Re: [gentoo-dev-announce] January 2010 meeting date Thomas Sachau
2009-12-25 5:10 ` Denis Dupeyron
2009-12-25 14:00 ` Thomas Sachau
2009-12-26 3:28 ` Doug Goldstein
2009-12-26 10:25 ` Fabian Groffen
2009-12-26 13:15 ` Thomas Sachau
2009-12-27 3:40 ` Zac Medico
2010-01-08 9:09 ` Mike Frysinger
2010-01-08 6:59 ` Mike Frysinger
2009-12-20 14:49 ` Fabian Groffen
2009-12-20 17:37 ` Jeremy Olexa
2009-12-20 20:01 ` Mike Frysinger
2009-12-20 20:04 ` Fabian Groffen
2009-12-21 3:16 ` Mike Frysinger
2009-12-21 7:54 ` Fabian Groffen
2009-12-21 11:30 ` Richard Freeman
2009-12-21 12:22 ` Fabian Groffen [this message]
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=20091221122209.GB3308@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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