From: "Hendricks, Kevin" <khendricks@ivey.uwo.ca>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
Tom Gall <gall@rochcivictheatre.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Getting things in... Was: Re: shifts on 64bit ints
Date: Fri, 04 Aug 2000 14:52:14 -0400 [thread overview]
Message-ID: <398B10DE.FE82BA4A@ivey.uwo.ca> (raw)
In-Reply-To: Pine.A41.3.96LJ1.1b7.1000804131713.33624A-100000@unlserve.unl.edu
Hi,
> I'm not really against the web site idea, but it's just that there won't
> be too many people submitting patches in the first place to warrent the
> extra administrative burden on developers with write access to BK, I would
> think.
I don't agree. A separate website is important. I don't work on the kernel
directly but I have submitted patches here and there and have run into problems
when testing/debugging the JDK that are kernel issues.
I don't want write access to any tree, but I do need to see what patches are
going in, what changed, the status of my own patches, etc.
Also, I think we could easily modify any of the simple bugdatabase programs like
bugzilla to do exactly what we want (instead of calling them bugs, call them
patches, instead of fixed, call them accepted, etc) You could also create
categories so that driver patches are separate from other patches easily with
this type of software.
We are getting more and more people contributing to the kernel process
I think a simple modified bugtracking system linked to http://penguinppc.org
could be easily made to serve this purpose without having/needing a whole new
site.
My two cents:
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-04 18:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <news-innominate.list.linux.ppc.dev@innominate.de>
2000-08-03 22:38 ` shifts on 64bit ints Thomas Graichen
2000-08-03 23:02 ` David Edelsohn
2000-08-03 23:54 ` Franz Sirl
2000-08-04 0:40 ` Takashi Oe
2000-08-04 0:50 ` Takashi Oe
2000-08-04 7:16 ` Thomas Graichen
2000-08-04 9:21 ` Gabriel Paubert
2000-08-04 15:18 ` David Edelsohn
2000-08-04 15:28 ` Kevin B. Hendricks
2000-08-04 16:06 ` Getting things in... Was: " Tom Gall
2000-08-04 16:26 ` David Edelsohn
2000-08-04 16:30 ` Tom Gall
2000-08-04 17:49 ` Benjamin Herrenschmidt
2000-08-04 18:32 ` Takashi Oe
2000-08-04 18:52 ` Hendricks, Kevin [this message]
2000-08-04 19:44 ` Takashi Oe
2000-08-04 20:10 ` Michael Schmitz
2000-08-05 5:42 ` Paul Mackerras
2000-08-05 11:51 ` Geert Uytterhoeven
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=398B10DE.FE82BA4A@ivey.uwo.ca \
--to=khendricks@ivey.uwo.ca \
--cc=bh40@calva.net \
--cc=gall@rochcivictheatre.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.edu \
/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 NNTP newsgroup(s).