mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: "Drew P. Vogel" <dvogel@intercarve.net>, Dave Jones <davej@suse.de>
Cc: <linux-kernel@vger.kernel.org>, patchbot-devel@killeri.net
Subject: Re: Public patch penguin
Date: Thu, 31 Jan 2002 04:32:45 +0100	[thread overview]
Message-ID: <E16W7xt-0000KX-00@starship.berlin> (raw)
In-Reply-To: <Pine.LNX.4.33.0201302042550.11522-100000@northface.intercarve.net>
In-Reply-To: <Pine.LNX.4.33.0201302042550.11522-100000@northface.intercarve.net>

On January 31, 2002 02:48 am, Drew P. Vogel wrote:
> > 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.

Hi Dave,

> Honestly I feel the same. Unfortunately installing new tools to do this is
> also a larger task than should be required. Personally, I would like a
> public ftp archive for patches to reside. I don't have a
> machine/connection I can open up ftp though.

Agreed.  Please have a look at what we're doing here:

   http://killeri.net/cgi-bin/alias/ezmlm-cgi

It's too early to try the code, currently at version 0.0 (thanks to Rasmus 
Andersen for that, Kalle Kivimaa for the mail list).  The guilding design 
rule is to do everything with MTAs that submitters and maintainers _are 
already using_, and to do it _just as they do it now_, using a normal mail 
archive as the data base.  The only thing that changes is: you mail the 
patchbot instead of the maintainer.

Submitters will need to put some minimal number of additional lines in the 
body of the email, and it's possible we'll get the 'minimal number' down to 
zero for common cases (one line description comes from subject, long 
description comes from mail, purpose is implied by [BUGFIX] in subject line, 
etc).

Do you see anything to object to so far?

-- 
Daniel

  reply	other threads:[~2002-01-31  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 17:56 Drew P. Vogel
2002-01-30 18:19 ` Dave Jones
2002-01-31  1:48   ` Drew P. Vogel
2002-01-31  3:32     ` Daniel Phillips [this message]
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=E16W7xt-0000KX-00@starship.berlin \
    --to=phillips@bonn-fries.net \
    --cc=davej@suse.de \
    --cc=dvogel@intercarve.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patchbot-devel@killeri.net \
    /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

all inboxes | Powered by JetHome®