From: Dave Jones <davej@suse.de>
To: "Drew P. Vogel" <dvogel@intercarve.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Public patch penguin
Date: Wed, 30 Jan 2002 19:19:38 +0100 [thread overview]
Message-ID: <20020130191937.N24012@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201301241300.9017-100000@northface.intercarve.net>
In-Reply-To: <Pine.LNX.4.33.0201301241300.9017-100000@northface.intercarve.net>; from dvogel@intercarve.net on Wed, Jan 30, 2002 at 12:56:21PM -0500
On Wed, Jan 30, 2002 at 12:56:21PM -0500, Drew P. Vogel wrote:
> Would there be any interest in a web site which hosts copies of all
> current patches, while providing a way to rate the patches and leave
> comments (a simplified freshmeat.net with only kernel patches).
It's been done before with various levels of success. Some would
like it, others (myself included) would likely not use it.
I've said it before, and I'll say it again. Any tool which requires
me to start up a web browser to do something productive is a major
nuisance.
> This would help facilitate the network of trust/cooperation Linus and others
> have suggested. Aside from the 10-20 people Linus works directly with, he
> and other maintainers could work with the site as the site will be a
> decent filter between Linus and the public. If 95% of users have a certain
> patch working without trouble against a particular tree, then the question
> first raised in this email becomes "very little".
I like the sounds of some of it. Take for example Andrew Mortons recent
ide-cd DMA patch. I was curious about how that worked out for people,
so I kept the whole thread. If at some point it's a candidate for
inclusion in my tree, I can open mutt, look in the January l-k folder,
and see the whole thread with success/failure stories, and see how it
worked out..
A correctly indexed patch repository could also duplicate this, but
not replace it. I do a lot of patch-hoovering scooping up mislaid
dropped patches from l-k archives when I'm on the road with no
network connection, or sitting around in hotel rooms watching bad
german television. For this reason, the www is a non-starter for me
unless I have some means of mirroring the whole repository and comments.
(which isn't too practical).
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-30 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 17:56 Public patch penguin Drew P. Vogel
2002-01-30 18:19 ` Dave Jones [this message]
2002-01-31 1:48 ` Drew P. Vogel
2002-01-31 3:32 ` Daniel Phillips
2002-01-31 16:09 ` Drew P. Vogel
2002-01-31 22:34 ` Daniel Phillips
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=20020130191937.N24012@suse.de \
--to=davej@suse.de \
--cc=dvogel@intercarve.net \
--cc=linux-kernel@vger.kernel.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