public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tod M. Neidt" <tneidt@fidnet.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Bugzilla... where to post ebuilds...
Date: 06 Jan 2002 12:51:23 -0600	[thread overview]
Message-ID: <1010343085.1174.2.camel@Q.neidt.net> (raw)
In-Reply-To: <1010342233.1005.0.camel@wp.smile>

 
> I don't find an file-selector there. Where can i upload files. e. g. to
> submit ebuilds? 
On the first page write the summary (usally name of ebuild) and the
description (be verbose). Commit that, and the next page has a link to
attach files. attache the ebuild as text.

Must ebuilds go to 'Ebuild' or to the specific product
New ebuilds go to ebuild. Hallski will then route it to the correct
place.

tod



  parent reply	other threads:[~2002-01-06 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 18:37 [gentoo-dev] Bugzilla... where to post ebuilds Sebastian Werner
2002-01-06 18:43 ` Einar Karttunen
2002-01-06 18:46 ` Chad M. Huneycutt
2002-01-06 20:17   ` mbutcher
2002-01-06 21:10     ` Sebastian Werner
2002-01-06 21:19     ` Mikael Hallendal
2002-01-06 18:51 ` Tod M. Neidt [this message]
2002-01-06 21:17 ` Mikael Hallendal

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=1010343085.1174.2.camel@Q.neidt.net \
    --to=tneidt@fidnet.com \
    --cc=gentoo-dev@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