Skip to contentSkip to conversation

mm/-next release on kernel.org web page?

DISCUSSION Dave Young 6 participants 14 messages Aug 2, 2009 – Aug 27, 2009

lore
Share & tools
lore

Dave Young

author
#0 lore raw

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

Signature · 2 lines
Regards
dave
#1 lore raw

Hi Dave,

Quoted 5 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young <[email protected]> wrote:

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

Each -next release appears as a patch relatively to Linus' at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/ . They come out basically each work day.

Signature · 3 lines
Cheers,
Stephen Rothwell                    [email protected]
http://www.canb.auug.org.au/~sfr/
author
#2 lore raw
Quoted 4 lines · Stephen Rothwell

Hi Dave,

Quoted 1 line · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young <[email protected]> wrote:
Quoted 8 lines
Quoted 4 lines

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

Each -next release appears as a patch relatively to Linus' at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/ .  They come out basically each work day.

Thanks for tell, Actually I know this address. But we can not get it from the www.kernel.org main page, isn't it? Could we put such link or guide info in the main page along with other releases?

Quoted 6 lines

--
Cheers,
Stephen Rothwell                    [email protected]
http://www.canb.auug.org.au/~sfr/

Signature · 2 lines
Regards
dave
#3 lore raw
In reply to Dave Young
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

The latest stable version of the Linux kernel is:           2.6.30.4
The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5
The latest 2.4 version of the Linux kernel is:              2.4.37.4
The latest 2.2 version of the Linux kernel is:              2.2.26
The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2
The latest -mm patch to the stable Linux kernels is:        2.6.28-rc2-mm1

mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4
next-20090731 ... applies to: v2.6.31-rc4

---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

author
#4 lore raw
Quoted 24 lines · Randy Dunlap
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

Quoted 8 lines

The latest stable version of the Linux kernel is:           2.6.30.4 The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5 The latest 2.4 version of the Linux kernel is:              2.4.37.4 The latest 2.2 version of the Linux kernel is:              2.2.26 The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2 The latest -mm patch to the stable Linux kernels is:        2.6.28-rc2-mm1 mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4
next-20090731 ... applies to: v2.6.31-rc4

Thanks randy. Very helpful. But I still have same question. Normal users need a more convenient and straightforward way to get what they want. It will be better that we put them on www.kernel.org main page, not only the version info but also the download link.

At least for me when I started my kernel hacking some years ago I always download kernel from www.kernel.org main page. I'm not sure whether others people do same thing. Current -next and mmtom are more like for us to do internal testing.

Quoted 7 lines

---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

Signature · 2 lines
Regards
dave
#5 lore raw
Quoted 39 lines · On Mon, 3 Aug 2009 10:08:40 +0800 Dave Young wrote:
Quoted 24 lines · Randy Dunlap
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

Quoted 8 lines

The latest stable version of the Linux kernel is:           2.6.30.4 The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5 The latest 2.4 version of the Linux kernel is:              2.4.37.4 The latest 2.2 version of the Linux kernel is:              2.2.26 The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2 The latest -mm patch to the stable Linux kernels is:        2.6.28-rc2-mm1 mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4
next-20090731 ... applies to: v2.6.31-rc4

Thanks randy. Very helpful. But I still have same question. Normal users need a more convenient and straightforward way to get what they want. It will be better that we put them on www.kernel.org main page, not only the version info but also the download link.

Quoted 4 lines

At least for me when I started my kernel hacking some years ago I always download kernel from www.kernel.org main page. I'm not sure whether others people do same thing. Current -next and mmtom are more like for us to do internal testing.

Oh, I agree with you, but [email protected] seems to be ignoring these emails (this is the third such one in the last 3-4 months).

---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

#6 lore raw
Quoted 39 lines · Randy Dunlap
Quoted 37 lines · On Mon, 3 Aug 2009 10:08:40 +0800 Dave Young wrote:
Quoted 23 lines · Randy Dunlap
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

Quoted 8 lines
The latest stable version of the Linux kernel is:           2.6.30.4
The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5
The latest 2.4 version of the Linux kernel is:              2.4.37.4
The latest 2.2 version of the Linux kernel is:              2.2.26
The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2
The latest -mm patch to the stable Linux kernels is:        2.6.28-rc2-mm1

mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4
next-20090731 ... applies to: v2.6.31-rc4

Thanks randy. Very helpful. But I still have same question. Normal users need a more convenient and straightforward way to get what they want. It will be better that we put them on www.kernel.org main page, not only the version info but also the download link.

Quoted 7 lines
Quoted 4 lines

At least for me when I started my kernel hacking some years ago I always download kernel from www.kernel.org main page. I'm not sure whether others people do same thing. Current -next and mmtom are more like for us to do internal testing.

Oh, I agree with you, but [email protected] seems to be ignoring these emails (this is the third such one in the last 3-4 months).

In fact we have been responding to these inquiries both to the public ones we have gotten (what we get added to on LKML), and to the private inquires, the latest one from LKML being a bit more than a week ago:

http://lkml.org/lkml/2009/7/24/334

We have been well aware of the problem for quite some time, the code base has rotted horribly, and the way kernel trees are placed in the hierarchy has changed from any reasonable assumption that was made many years ago when the code was first put together. We (meaning me) are, literally, in the middle of revamping this code, however it's basically a complete re-write of the code base at this point.

And in the last few weeks we've been dealing with quite a lot on top of trying to make forward progress on this code base, like the Bind DNS vulnerabilities, OSCon, Linux Symposium and the plethora of other things that need doing. Really, we aren't ignoring the problem, there's just one of me and a lot to do and I'm plugging away at it all. Please be patient, I'm trying to get it done and up and running. Until then *PLEASE* bear with us while we get through everything.

- John 'Warthog9' Hawley

#7 lore raw
Quoted 50 lines · J.H.
Quoted 39 lines · Randy Dunlap
Quoted 37 lines · On Mon, 3 Aug 2009 10:08:40 +0800 Dave Young wrote:
Quoted 23 lines · Randy Dunlap
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

Quoted 8 lines
The latest stable version of the Linux kernel is:           2.6.30.4
The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5
The latest 2.4 version of the Linux kernel is:              2.4.37.4
The latest 2.2 version of the Linux kernel is:              2.2.26
The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2
The latest -mm patch to the stable Linux kernels is:        2.6.28-rc2-mm1

mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4
next-20090731 ... applies to: v2.6.31-rc4

Thanks randy. Very helpful. But I still have same question. Normal users need a more convenient and straightforward way to get what they want. It will be better that we put them on www.kernel.org main page, not only the version info but also the download link.

Quoted 7 lines
Quoted 4 lines

At least for me when I started my kernel hacking some years ago I always download kernel from www.kernel.org main page. I'm not sure whether others people do same thing. Current -next and mmtom are more like for us to do internal testing.

Oh, I agree with you, but [email protected] seems to be ignoring these emails (this is the third such one in the last 3-4 months).

In fact we have been responding to these inquiries both to the public ones we have gotten (what we get added to on LKML), and to the private inquires, the latest one from LKML being a bit more than a week ago:

Quoted 8 lines

http://lkml.org/lkml/2009/7/24/334

We have been well aware of the problem for quite some time, the code base has rotted horribly, and the way kernel trees are placed in the hierarchy has changed from any reasonable assumption that was made many years ago when the code was first put together. We (meaning me) are, literally, in the middle of revamping this code, however it's basically a complete re-write of the code base at this point.

And in the last few weeks we've been dealing with quite a lot on top of trying to make forward progress on this code base, like the Bind DNS vulnerabilities, OSCon, Linux Symposium and the plethora of other things that need doing. Really, we aren't ignoring the problem, there's just one of me and a lot to do and I'm plugging away at it all. Please be patient, I'm trying to get it done and up and running. Until then *PLEASE* bear with us while we get through everything.

- John 'Warthog9' Hawley

Not to reply to myself, but I've pushed out an update that should incorporate the expected trees now, this does eliminate the 2.2 and all but the last 2.4 tree (2.4.37.5), but does include all of the stable 2.6.x trees, the snapshots and linux-next. Frontpage, finger and rss should all be showing the new information universally. I'll probably tweak things a bit more (layout and such for the rss & html) but the kernels should now be listed as people expect.

- John 'Warthog9' Hawley
Chief Kernel.org Administrator

#8 lore raw
Quoted 8 lines · J.H.

Not to reply to myself, but I've pushed out an update that should incorporate the expected trees now, this does eliminate the 2.2 and all but the last 2.4 tree (2.4.37.5), but does include all of the stable 2.6.x trees, the snapshots and linux-next. Frontpage, finger and rss should all be showing the new information universally. I'll probably tweak things a bit more (layout and such for the rss & html) but the kernels should now be listed as people expect.

This looks a lot better, thanks. But note that the 2.6.28 and 2.6.29 stable series are no longer maintained, and the current versions of them have known security issues, so it might not be a good idea to show that they are recommended for use at all.

Is there some way that we can "mark" activly maintained releases to have them show up on the front page in any way? We can use the LATEST-IS type file in the kernel directory if you want, that would be a simple way to maintain this information.

thanks,

greg k-h

#9 lore raw
Quoted 8 lines · Greg KH
Quoted 1 line · J.H.

Not to reply to myself, but I've pushed out an update that should incorporate the expected trees now, this does eliminate the 2.2 and all but the last 2.4 tree (2.4.37.5), but does include all of the stable 2.6.x trees, the snapshots and linux-next. Frontpage, finger and rss should all be showing the new information universally. I'll probably tweak things a bit more (layout and such for the rss & html) but the kernels should now be listed as people expect.

This looks a lot better, thanks. But note that the 2.6.28 and 2.6.29 stable series are no longer maintained, and the current versions of them have known security issues, so it might not be a good idea to show that they are recommended for use at all.

Quoted 4 lines

Is there some way that we can "mark" activly maintained releases to have them show up on the front page in any way? We can use the LATEST-IS type file in the kernel directory if you want, that would be a simple way to maintain this information.

The way the script works, in particular with regards to the ever changing realm of the 'stable' trees is this:

Wander the entire stable directory looking for git trees that have a tag that was last produced within 6 months (this can be shortened/lengthened but 6 months seemed reasonable at the time). Pull the information for those kernels out and show them. 2.6.28's last tag was 3 months ago, 2.6.29's was 7 weeks ago (almost 2 months) but things like 2.6.27 had an update 10 days ago.

I would be a bit concerned about using the LATEST-IS tags in the kernel directory, in particular there are external scripts that snag the LATEST-IS file to determine if a kernel needs to be pulled in, etc. Having multiple of those files would likely play havoc with those scripts as I'm sure they are doing something like:

ncftpget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/LATEST-IS-*

It might also be particularly confusing to people to see multiple LATEST-IS'

Could do something based on the specific git tag for a tree, something like tagging the tree EOL would remove it from the list immediately, would have the advantage that should development be picked-back up and a new tag get created it would automatically show back up in the list, as well as it being explicit that that stable tree had stopped development.

For things like 2.6.28 & 2.6.29 that have more serious security vulnerabilities could setup some sort of blacklist file, or even a file that you could touch in the repo's directory that would blacklist it as well.

Like said, can always shorten the expiry period from 6 months to 3 for example which would more aggressively prune the list too.

Thoughts?

- John 'Warthog9' Hawley

author
#10 lore raw
In reply to J.H.
Quoted 85 lines · J.H.
Quoted 80 lines · J.H.
Quoted 49 lines · Randy Dunlap
Quoted 46 lines · On Mon, 3 Aug 2009 10:08:40 +0800 Dave Young wrote:
Quoted 29 lines · Randy Dunlap
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my
http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

Quoted 9 lines

The latest stable version of the Linux kernel is:           2.6.30.4 The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5 The latest 2.4 version of the Linux kernel is:              2.4.37.4 The latest 2.2 version of the Linux kernel is:              2.2.26 The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2 The latest -mm patch to the stable Linux kernels is:
 2.6.28-rc2-mm1
mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4 next-20090731 ... applies to: v2.6.31-rc4

Thanks randy. Very helpful. But I still have same question. Normal users need a more convenient and straightforward  way to get what they want.  It will be better that we put them on www.kernel.org main page, not only the version info but also the download link.

Quoted 7 lines
Quoted 4 lines

At least for me when I started my kernel hacking some years ago I always download kernel from www.kernel.org main page. I'm not sure whether others people do same thing. Current -next and mmtom are more like for us to do internal testing.

Oh, I agree with you, but [email protected] seems to be ignoring these emails (this is the third such one in the last 3-4 months).

In fact we have been responding to these inquiries both to the public ones we have gotten (what we get added to on LKML), and to the private inquires, the latest one from LKML being a bit more than a week ago:

http://lkml.org/lkml/2009/7/24/334

We have been well aware of the problem for quite some time, the code base has rotted horribly, and the way kernel trees are placed in the hierarchy has changed from any reasonable assumption that was made many years ago when the code was first put together.  We (meaning me) are, literally, in the middle of revamping this code, however it's basically a complete re-write of the code base at this point.

And in the last few weeks we've been dealing with quite a lot on top of trying to make forward progress on this code base, like the Bind DNS vulnerabilities, OSCon, Linux Symposium and the plethora of other things that need doing.  Really, we aren't ignoring the problem, there's just one of me and a lot to do and I'm plugging away at it all.  Please be patient, I'm trying to get it done and up and running.  Until then *PLEASE* bear with us while we get through everything.

Quoted 2 lines

- John 'Warthog9' Hawley

Quoted 7 lines

Not to reply to myself, but I've pushed out an update that should incorporate the expected trees now, this does eliminate the 2.2 and all but the last 2.4 tree (2.4.37.5), but does include all of the stable 2.6.x trees, the snapshots and linux-next.  Frontpage, finger and rss should all be showing the new information universally.  I'll probably tweak things a bit more (layout and such for the rss & html) but the kernels should now be listed as people expect.

Thanks for your work.

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

Quoted 4 lines

- John 'Warthog9' Hawley
Chief Kernel.org Administrator

Signature · 2 lines
Regards
dave
#11 lore raw
Quoted 94 lines · On Thu, 27 Aug 2009 22:39:13 +0800 Dave Young wrote:
Quoted 85 lines · J.H.
Quoted 80 lines · J.H.
Quoted 49 lines · Randy Dunlap
Quoted 46 lines · On Mon, 3 Aug 2009 10:08:40 +0800 Dave Young wrote:
Quoted 29 lines · Randy Dunlap
Quoted 9 lines · On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young wrote:

Hi,

The last mm patchset is 2.6.28-rc2-mm1. We can not download -mm patchset from kernel.org web page since the -next tree born.

Could you consider put mmtom release there just like before? And even -next tree patchset? It will be more convenient for users who test kernel just by downloading from web. Now it's impossible for them to test these patchsets because they normally do not subscribe to lkml.

from www.kernel.org:
For comments about the web pages, please send mail to [email protected].

also from www.kernel.org:
Please don't use finger.kernel.org for any sort of automatic monitoring. The number of automatic bots hitting this port is causing the finger daemon to shut down more often than not. The same information is available from http://www.kernel.org/kdist/finger_banner.

and of course the finger_banner file is not up to date.

You may consider using my
http://www.xenotime.net/linux/scripts/kcurrent script. Its output (today) is:

Quoted 9 lines

The latest stable version of the Linux kernel is:           2.6.30.4 The latest prepatch for the stable Linux kernel tree is:    2.6.31-rc5 The latest 2.4 version of the Linux kernel is:              2.4.37.4 The latest 2.2 version of the Linux kernel is:              2.2.26 The latest prepatch for the 2.2 Linux kernel tree is:       2.2.27-rc2 The latest -mm patch to the stable Linux kernels is:
 2.6.28-rc2-mm1
mmotm-2009-0730-0501 ... applies to: 2.6.31-rc4 next-20090731 ... applies to: v2.6.31-rc4

Thanks randy. Very helpful. But I still have same question. Normal users need a more convenient and straightforward  way to get what they want.  It will be better that we put them on www.kernel.org main page, not only the version info but also the download link.

Quoted 7 lines
Quoted 4 lines

At least for me when I started my kernel hacking some years ago I always download kernel from www.kernel.org main page. I'm not sure whether others people do same thing. Current -next and mmtom are more like for us to do internal testing.

Oh, I agree with you, but [email protected] seems to be ignoring these emails (this is the third such one in the last 3-4 months).

In fact we have been responding to these inquiries both to the public ones we have gotten (what we get added to on LKML), and to the private inquires, the latest one from LKML being a bit more than a week ago:

http://lkml.org/lkml/2009/7/24/334

We have been well aware of the problem for quite some time, the code base has rotted horribly, and the way kernel trees are placed in the hierarchy has changed from any reasonable assumption that was made many years ago when the code was first put together.  We (meaning me) are, literally, in the middle of revamping this code, however it's basically a complete re-write of the code base at this point.

And in the last few weeks we've been dealing with quite a lot on top of trying to make forward progress on this code base, like the Bind DNS vulnerabilities, OSCon, Linux Symposium and the plethora of other things that need doing.  Really, we aren't ignoring the problem, there's just one of me and a lot to do and I'm plugging away at it all.  Please be patient, I'm trying to get it done and up and running.  Until then *PLEASE* bear with us while we get through everything.

Quoted 2 lines

- John 'Warthog9' Hawley

Quoted 7 lines

Not to reply to myself, but I've pushed out an update that should incorporate the expected trees now, this does eliminate the 2.2 and all but the last 2.4 tree (2.4.37.5), but does include all of the stable 2.6.x trees, the snapshots and linux-next.  Frontpage, finger and rss should all be showing the new information universally.  I'll probably tweak things a bit more (layout and such for the rss & html) but the kernels should now be listed as people expect.

Quoted 1 line

Thanks for your work.

Yes, thanks. Much better.

Quoted 2 lines

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

Ditto. Please.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

#12 lore raw
Quoted 4 lines
Quoted 2 lines

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

#13 lore raw
Quoted 5 lines · On Thu, 27 Aug 2009 13:57:57 -0700 "J.H." <[email protected]> wrote:
Quoted 4 lines
Quoted 2 lines

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

Ditto. Please.

Quoted 8 lines

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.

Well, it'd be simple enough to stick it all in a different directory. But I need to find a way to shove most of -mm into linux-next, after which it all becomes a bit moot.