public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Status report: Gentoo PHP packages
Date: Tue, 23 Aug 2005 19:25:19 +0100	[thread overview]
Message-ID: <1124821519.6017.65.camel@mogheiden.gnqs.org> (raw)
In-Reply-To: <20050822203837.3a564975@enterprise.weeve.org>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Mon, 2005-08-22 at 20:38 -0600, Jason Wever wrote:
> Is there a reason you folks are using a non-gentoo bug system to work on
> this?  It seems a bit redundant and un-needed in my layman's
> perspective.
> 
> Cheers,

Gentoo's bugzilla doesn't seem to be the place to log bugs about
packages that aren't in the Portage tree.  Trac's ticketing system
integrates well with subversion's change history.  The overlay will
continue to be where the majority of the PHP team's work happens, and
we'll periodically bring a subset of the overlay over into Portage.

Best regards,
Stu
-- 
Stuart Herbert                                         stuart@gentoo.org
Gentoo Developer                                  http://www.gentoo.org/
                                              http://stu.gnqs.org/diary/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-08-23 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 22:27 [gentoo-dev] Status report: Gentoo PHP packages Stuart Herbert
2005-08-23  2:38 ` Jason Wever
2005-08-23 18:25   ` Stuart Herbert [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=1124821519.6017.65.camel@mogheiden.gnqs.org \
    --to=stuart@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