public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Theo Chatzimichos <tampakrap@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] proposal for reducing of cross-posting
Date: Tue, 30 Oct 2012 16:41:05 +0100	[thread overview]
Message-ID: <CAPDe-1NLRncQ+JEx_TgZEF_CTpLuokj544YNA10BL1i8KXCHJA@mail.gmail.com> (raw)

Hello,

I would like to propose the two following things:
1) to stop cross-posting between gentoo-dev and gentoo-dev-announce.
gentoo-dev-announce has reply-to gentoo-dev, I see no reason for
cross-posting.
2) to stop cross-posting for council announcements between
gentoo-dev-announce and gentoo-project, and instead to post them only
in gentoo-dev-announce and not use gentoo-project for council at all,
because they are mails regarding technical issues, while
gentoo-project is a list decidated to non-technical discussions.
Opinions?

Theo


             reply	other threads:[~2012-10-30 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 15:41 Theo Chatzimichos [this message]
2012-10-30 15:58 ` [gentoo-project] proposal for reducing of cross-posting Sergey Popov
2012-10-31  7:36 ` Ben de Groot
2012-10-31 17:08   ` Theo Chatzimichos
2012-11-01 12:18 ` Petteri Räty

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=CAPDe-1NLRncQ+JEx_TgZEF_CTpLuokj544YNA10BL1i8KXCHJA@mail.gmail.com \
    --to=tampakrap@gentoo.org \
    --cc=gentoo-project@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