From: Renat Golubchyk <ragermany@gmx.net>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Simulation software package maintainer
Date: Thu, 23 Nov 2006 03:46:48 +0100 [thread overview]
Message-ID: <20061123034648.66f6d381@mating-tux> (raw)
In-Reply-To: <8e8ee0d40611221309j54847546xc269d9018043613d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
Hi!
On Wed, 22 Nov 2006 22:09:34 +0100 "Paul Cochrane"
<paultcochrane@gmail.com> wrote:
> Is this the correct way to go about getting a new package into Gentoo
> while remaining an upstream author and not a package maintainer as
> such?
The proper way is to go to bugs.gentoo.org and open a new bug with the
request.
Cheers,
Renat
--
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
(Einstein)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2006-11-23 2:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 21:09 [gentoo-science] Simulation software package maintainer Paul Cochrane
2006-11-23 2:46 ` Renat Golubchyk [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=20061123034648.66f6d381@mating-tux \
--to=ragermany@gmx.net \
--cc=gentoo-science@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