From: Benjamin Herrenschmidt <bh40@calva.net>
To: Tom Gall <gall@rochcivictheatre.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Getting things in... Was: Re: shifts on 64bit ints
Date: Fri, 4 Aug 2000 19:49:53 +0200 [thread overview]
Message-ID: <20000804174953.16973@mailhost.mipsys.com> (raw)
In-Reply-To: <398AEA0C.329AB669@rochcivictheatre.org>
>
> I must confess this is one of those areas where I wish we were on CVS
>instead of BK.
>
> If you want feel free to send your patches my way and I'll be sure
>that they get in. I can at least test things on my prep, chrp rs6000s
>and even my power mac.
>
>> linuxppc-dev is not necessarily a patch submission mailinglist.
>> Until PowerPC Linux development has such a thing, I think that it is
>> better to coordinate with and directly send patches to someone with
>> write-access who can apply the patches instead of throwing them up in the
>> air and hoping that someone catches them.
>
> This can be a good thing or a bad thing tho. I'd rather like to see
>patches posted to the list. Granted there's some line there where they
>simply get too big and a link is better. At least with posting to the
>list everyone has the chance to comment and better yet test them out!
I'm an horribly bad web designer, but one cool thing to do if someone is
good at it, would be a web-pased patch repository. You send patches with
a web form (eventually an upload mecanism) along with your email, a
comment, etc..., they get assigned a patch number automatically, anybody
can consult the database, and people with write access to BK can mark
them (accepted, refused, postponed, ... along with a comment) once they
have been handled.
Any volunteer to design such a site ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-04 17:49 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 [this message]
2000-08-04 18:32 ` Takashi Oe
2000-08-04 18:52 ` Hendricks, Kevin
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=20000804174953.16973@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=gall@rochcivictheatre.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).