From: Gary Thomas <gary@mlbassoc.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Patch policy
Date: Tue, 06 May 2003 13:34:00 -0000 [thread overview]
Message-ID: <1052228094.30126.4510.camel@hermes> (raw)
In-Reply-To: <20030506132550.GK24032@biferten.ma.tech.ascom.ch>
On Tue, 2003-05-06 at 07:25, Andrew Lunn wrote:
> > In an ideal world, patches from outside our group would
> > be posted to a database which could be queried by anyone.
> > Maybe the easiest way to do this would be to forward the
> > patch to BugZilla.
>
> Sounds like a reasonable idea. Let bugzilla pick the default owner of
> the patch depending on the component. We would probably want to add
> more HAL components, one per architecture.
>
> The messy thing is getting the patch from ecos-patches into
> bugzilla. I don't see it being done automagically. Do we have to
> retrain all contributers to use bugzilla instead of the list? Does one
> of us have to import the patch?
>
This is policy that we would have to develop (decide on).
One way would be to only accept patches via BugZilla. Then the
onus would be on the submitter. To make this policy work, maybe
we'd want to have the default owner of the "bug" be the patches
list, or at least send a copy there.
Anyway, it's just an idea that I think we can mull over a bit.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next prev parent reply other threads:[~2003-05-06 13:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 12:59 Gary Thomas
2003-05-06 13:17 ` Mark Salter
2003-05-06 13:26 ` Andrew Lunn
2003-05-06 13:34 ` Gary Thomas [this message]
2003-05-06 13:40 ` Andrew Lunn
2003-05-06 13:44 ` Gary Thomas
2003-05-06 14:51 ` Jonathan Larmour
2003-05-06 14:46 ` Jonathan Larmour
2003-05-07 20:30 ` Jonathan Larmour
2003-05-07 21:54 ` Gary Thomas
2003-05-07 22:48 ` Alex Schuilenburg
2003-05-07 23:02 ` Jonathan Larmour
2003-05-07 23:39 ` Alex Schuilenburg
2003-05-07 23:55 ` Jonathan Larmour
2003-05-08 0:18 ` Alex Schuilenburg
2003-05-08 3:16 ` Jonathan Larmour
2003-05-08 9:45 ` Alex Schuilenburg
2003-05-07 23:27 ` Alex Schuilenburg
2003-05-06 15:00 ` Jonathan Larmour
2003-05-06 15:06 ` Gary Thomas
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=1052228094.30126.4510.camel@hermes \
--to=gary@mlbassoc.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.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).