public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Gary Thomas <gary@mlbassoc.com>,
	eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Patch policy
Date: Tue, 06 May 2003 14:46:00 -0000	[thread overview]
Message-ID: <3EB7CAAF.4050807@eCosCentric.com> (raw)
In-Reply-To: <20030506132550.GK24032@biferten.ma.tech.ascom.ch>

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?

I'd suggest not using bugzilla actually. I've already been thinking about 
this problem and there are well established patch managers out there. In 
particular I'm thinking of what is on savannah.gnu.org, e.g.: 
http://savannah.gnu.org/patch/?group=inetutils

I think is is a brilliant, and obviously being purpose-built, ideally 
suited solution. My hope is that we can move straight to using this if we 
become a GNU project.

But I didn't bother suggesting it yet :-).

If we don't become a GNU project, we could see about bringing it onto 
sources.redhat.com ( or ecos.sourceware.org if you like :-)).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

  parent reply	other threads:[~2003-05-06 14:46 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
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 [this message]
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=3EB7CAAF.4050807@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.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).