linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@linuxcare.com.au>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: Tom Gall <gall@rochcivictheatre.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Getting things in...  Was: Re: shifts on 64bit ints
Date: Sat, 5 Aug 2000 15:42:01 +1000 (EST)	[thread overview]
Message-ID: <14731.43305.438998.169473@argo.linuxcare.com.au> (raw)
In-Reply-To: <20000804174953.16973@mailhost.mipsys.com>


Benjamin Herrenschmidt writes:

> 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.

Sounds exactly like the jitterbug site that Andrew Tridgell set up for
the Linux kernel.  Linus tried it for a while but unfortunately
eventually decided he didn't like it enough.  But for the rest of us
it was great.  Tridge even put in a "test patch" button for Linus that
would rsync the current kernel tree, automagically unpack/decompress
the patch, apply it and report any errors.  I could ask Tridge to set
up something like this for us.

Paul.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-08-05  5:42 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
2000-08-04 19:44                     ` Takashi Oe
2000-08-04 20:10                     ` Michael Schmitz
2000-08-05  5:42                 ` Paul Mackerras [this message]
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=14731.43305.438998.169473@argo.linuxcare.com.au \
    --to=paulus@linuxcare.com.au \
    --cc=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).