From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, webmaster@kernel.org
Subject: Re: No full image on kernel.org home page.
Date: Thu, 26 May 2005 15:43:23 +0200 [thread overview]
Message-ID: <4295D27B.1030309@ens-lyon.org> (raw)
In-Reply-To: <1117114714.4313.21.camel@localhost.localdomain>
Try the "F" link on the right.
Brice
Steven Rostedt a écrit :
> Hi all,
>
> Just wondering why there's only patches to download from the kernel.org
> home page? It would be nice if you could also download the image that
> you needed to patch against. I know I can easily get the images by
> cruising down the links of either the HTML or FTP.
>
> If the full image is not there to have people use the patches more
> often, then it would make more sense to have a link on the main page to
> the image to patch against. If I have to make the effort to follow the
> links down to get a image, I'll just take the full image of the one I
> want instead of the patch. This means that the next time I get a image,
> I need to download the whole thing again.
>
> So having something like this:
>
> The latest stable version of the Linux kernel is: 2.6.11.10 (patched against 2.6.11)
>
> Having the 2.6.11.10 be a link to the patch and 2.6.11 the full bz2
> image tar ball. When I get a image I would get the 2.6.11, then the
> patch. The next time I would only need to get the patch. Otherwise,
> being lazy and a procrastinator, I would follow the links and download
> the 2.6.11.10 tarball. (lazy since I don't need to do any patching, a
> procrastinator since I could have downloaded the 2.6.11 to patch against
> next time but just say "I'll do that later!").
>
> Cheers,
>
> -- Steve
next prev parent reply other threads:[~2005-05-26 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 13:38 No full image on kernel.org home page Steven Rostedt
2005-05-26 13:43 ` Brice Goglin [this message]
2005-05-26 13:49 ` Steven Rostedt
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=4295D27B.1030309@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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