From: Gary Thomas <gary@mlbassoc.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Jonathan Larmour <jifl@ecoscentric.com>,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Doc on How to submit patches
Date: Wed, 03 Sep 2003 12:48:00 -0000 [thread overview]
Message-ID: <1062593283.20604.1570.camel@hermes> (raw)
In-Reply-To: <20030903123432.GK6488@biferten.ma.tech.ascom.ch>
On Wed, 2003-09-03 at 06:34, Andrew Lunn wrote:
> On Wed, Sep 03, 2003 at 12:08:40AM +0100, Jonathan Larmour wrote:
> > Nick and myself have been working on this:
> > http://ecos.sourceware.org/patches.html
> >
> > Comments? Corrections? Abuse?
>
> The component to use in Bugzilla is "Patches and Contributions". Im
> humming and harring as to if it would be better to use the component
> the major part of the patch is in. That way it automagically gets a
> default owner who we can point a finger at when the patch sits around
> for a while with nothing happening. If the owner is overloaded its his
> responsibility to then find another maintainer to take over the patch.
>
> It would be nice to add a state "Waiting for assignment" to bugzilla.
>
Isn't this just the "new" state? Once it has been looked at by
someone, it should then be assigned (as appropriate) and changed to
"assigned" or "needinfo".
We currently have too many bugs that are just left at "new" (some in
the old system were 3-4 years old!). I think they should be moved to
a working status as soon as possible and yes, I know, I'm at least
as guilty as anyone else in this regard.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next prev parent reply other threads:[~2003-09-03 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 23:08 Jonathan Larmour
2003-09-03 2:57 ` Gary Thomas
2003-09-03 12:34 ` Andrew Lunn
2003-09-03 12:48 ` Gary Thomas [this message]
2003-09-03 14:21 ` Jonathan Larmour
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=1062593283.20604.1570.camel@hermes \
--to=gary@mlbassoc.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).