public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastien Fabbro <seb@ist.utl.pt>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] website python error
Date: Fri, 15 Sep 2006 10:05:52 +0100	[thread overview]
Message-ID: <450A6CF0.4080006@ist.utl.pt> (raw)
In-Reply-To: <450A2A6C.6050205@gentoo.org>

If overlays.g.o has better support, I back up Donnie's suggestion.

I cannot close the "Trac tickets" on the gentooscience overlay of the 
ebuilds I commit and I don't receive any notification a new ticket 
arrived. To track an ebuild, I usually file a bug on bugs.g.o, but it is 
not very practical to keep trac of an ebuild on two sites.
Many of the gentooscience tickets could be closed. Other than a svn 
repository, it does not do much else.

I guess the other sci herd testers have the same problems.

Sebastien

Donnie Berkholz wrote:
> Pretty sure they're not interested in linking to external overlays. If
> you want a link, and to save some time on maintenance and future
> breakage, it might be easier to just migrate to their hosting.
> 
> Thanks,
> Donnie
> 

-- 
gentoo-science@gentoo.org mailing list



  parent reply	other threads:[~2006-09-15  9:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 13:35 [gentoo-science] website python error Nuno Sucena Almeida
2006-09-13 14:07 ` Andrey G. Grozin
2006-09-14 10:24   ` Marcus D. Hanwell
2006-09-14 10:49     ` Andrey G. Grozin
2006-09-14 11:19       ` Marcus D. Hanwell
2006-09-15  4:22     ` Donnie Berkholz
2006-09-15  7:50       ` Andrey G. Grozin
2006-09-15 11:57         ` Marcus D. Hanwell
2006-09-16  8:51           ` Andrey G. Grozin
2006-09-18  7:43             ` Marcus D. Hanwell
2006-09-18  7:24               ` Donnie Berkholz
2006-09-18  7:27                 ` Donnie Berkholz
2006-09-18  8:40               ` Jan Marten Simons
2006-09-21 13:53               ` Andrey G. Grozin
2006-09-15  9:05       ` Sebastien Fabbro [this message]
2006-09-15 11:51       ` Marcus D. Hanwell

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=450A6CF0.4080006@ist.utl.pt \
    --to=seb@ist.utl.pt \
    --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