From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] OSS-QM again ...
Date: Tue, 17 Aug 2010 15:55:25 -0400 [thread overview]
Message-ID: <AANLkTi=-rnr6HpZtR4wRBr2chE6Z7FZiEwScR3XCB_6t@mail.gmail.com> (raw)
In-Reply-To: <20100817155849.GA24806@nibiru.local>
On Tue, Aug 17, 2010 at 11:58 AM, Enrico Weigelt wrote:
> That's yet another reason why I'd like package maintainers to
> push their changes into the oss-qm repo. That would be a great
> help for others having to deal with the same package.
nothing is stopping individual maintainers from contributing to your
project. however, that doesnt mean you need to keep broadcasting
updates to an unrelated list (like any Gentoo list). start your own
mailing list and get people to subscribe to it.
-mike
next prev parent reply other threads:[~2010-08-17 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 15:58 [gentoo-dev] OSS-QM again Enrico Weigelt
2010-08-17 16:44 ` Jeroen Roovers
2010-08-17 17:09 ` Jeroen Roovers
2010-08-17 19:55 ` Mike Frysinger [this message]
2010-08-18 1:06 ` [gentoo-dev] " Duncan
2010-08-18 19:15 ` Enrico Weigelt
2010-08-20 16:48 ` Enrico Weigelt
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='AANLkTi=-rnr6HpZtR4wRBr2chE6Z7FZiEwScR3XCB_6t@mail.gmail.com' \
--to=vapier@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