public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.H." <warthog9@kernel.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Dave Young <hidave.darkstar@gmail.com>,
	webmaster@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>,
	stable@kernel.org
Subject: Re: mm/-next release on kernel.org web page?
Date: Thu, 27 Aug 2009 13:57:57 -0700	[thread overview]
Message-ID: <4A96F355.30808@kernel.org> (raw)
In-Reply-To: <20090827124315.0d0f2129.rdunlap@xenotime.net>

>> Is it possible to add latest mmotm link?
>> Just link to andrew's broken-out.tar.gz with the stamp name?
> 
> Ditto.  Please.

Problem with mmotm is that Andrew is hosting that out of his public_html 
directory, which I can only assume means that the tree isn't intended to 
be consumed by the masses, as official trees are supposed to live under 
/pub.  If this is not the case then we need to get it moved under 
/pub/scm & /pub as things on public_html aren't synced out to the 
front-end machines.  But I will have to defer to Andrew on what 
direction he wants to take mmotm.

- John 'Warthog9' Hawley

  reply	other threads:[~2009-08-27 20:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-02  7:56 mm/-next release on kernel.org web page? Dave Young
2009-08-02 14:48 ` Stephen Rothwell
2009-08-03  1:54   ` Dave Young
2009-08-02 16:55 ` Randy Dunlap
2009-08-03  2:08   ` Dave Young
2009-08-03  2:30     ` Randy Dunlap
2009-08-03  5:01       ` J.H.
2009-08-27  0:42         ` J.H.
2009-08-27  3:33           ` Greg KH
2009-08-27 22:03             ` J.H.
2009-08-27 14:39           ` Dave Young
2009-08-27 19:43             ` Randy Dunlap
2009-08-27 20:57               ` J.H. [this message]
2009-08-27 21:46                 ` Andrew Morton

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=4A96F355.30808@kernel.org \
    --to=warthog9@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stable@kernel.org \
    --cc=webmaster@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