public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Jonathan Larmour <jifl@ecoscentric.com>,
	Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Bugzilla
Date: Wed, 23 Apr 2003 15:25:00 -0000	[thread overview]
Message-ID: <3EA6B06F.6010908@ecoscentric.com> (raw)
In-Reply-To: <3EA68D45.1060606@eCosCentric.com>

Jonathan Larmour wrote:
> Andrew Lunn wrote:
> 
>>> Here's what it looks like now: http://bugzilla.ecoscentric.com/ but 
>>> obviously it shouldn't be explicitly ecoscentric.com, so I suggest we 
>>> get bugs.ecos.sourceware.org and/or later on bugs.ecos.gnu.org set up 
>>> as aliases so no-one should know what machine it actually lives on. 
>>> If you look at the "new bug" page you can see Alex has even added all 
>>> the version numbers/platforms etc. so you can see what it looks like.
>>
>>
>>
>> Its missing a few versions. eg anoncvs-head, 2.0-branch-head. 
> 
> 
> Easy to fix.

and you can now do it yourself.  I have granted you all the relevant 
permissions to add components/versions/etc :-)

> 
> Note it isn't live yet.... I was only suggesting we switch over later, 
> not now :-). We can keep the bugs that have already been submitted, but 
> for now, keep using Red Hat's bugzilla.

And just to add to this, I am have started the process of importing the 
old public prms bugs as well as the old public CRs.  After that, I will 
transfer over the bugs from the red hat site, closing each as they are 
transferred, before closing the public ecos view on RH's site.

I have pretty much finished ecos site customizations (layout and 
content) for now.

I have also not applied the patches I created for bz last year (allowing 
easy maintainer addition of platforms and architectures) since it looks 
like the next release of bz will contain alternative fixes.  For now, 
adding new platforms and architectures will need to be done through a 
simple script.

Feedback is appreciated.
-- Alex


      reply	other threads:[~2003-04-23 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 23:26 Bugzilla Jonathan Larmour
2003-04-23  8:31 ` Bugzilla Andrew Lunn
2003-04-23 12:55   ` Bugzilla Jonathan Larmour
2003-04-23 15:25     ` Alex Schuilenburg [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=3EA6B06F.6010908@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jifl@ecoscentric.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).