From: Al Boldi <a1426z@gawab.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org
Subject: Re: Linux 2.6.29.5
Date: Tue, 16 Jun 2009 18:02:43 +0300 [thread overview]
Message-ID: <200906161802.43349.a1426z@gawab.com> (raw)
In-Reply-To: <20090616051415.GA30708@suse.de>
Greg KH wrote:
> On Tue, Jun 16, 2009 at 07:33:57AM +0300, Al Boldi wrote:
> > > > It may be a good idea to also allow pulling patches over email.
> > >
> > > I'm confused as to why you would want this. kernel.org is mirrored all
> > > around the world, so the tree can be found through ftp and http
> > > everywhere.
> >
> > Sometimes the only ports open are 110 and 25.
>
> That would not sound like an environment in which kernel development can
> happen very easily.
>
> > > > Majordomo has such a facility via the "index" and "get" commands.
> > >
> > > Majordomo is not used here for email delivery.
> >
> > Strange, vger.kernel.org sends via majordomo.
>
> For subscribing to lists only, not for email delivery.
Right, so the infrastructure is in place to support pulling patches via email
by simply sending the line "get linux-kernel patch-2.6.29.5.bz2" in
the body of a message to majordomo@vger.kernel.org.
All that is needed now is to populate those dirs.
Thanks!
--
Al
prev parent reply other threads:[~2009-06-16 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 20:03 Linux 2.6.29.5 Greg KH
2009-06-15 20:03 ` Greg KH
2009-06-16 3:48 ` Al Boldi
2009-06-16 3:56 ` Greg KH
2009-06-16 4:33 ` Al Boldi
2009-06-16 5:14 ` Greg KH
2009-06-16 15:02 ` Al Boldi [this message]
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=200906161802.43349.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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