From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Announce: daily 2.5 BK snapshots
Date: Thu, 08 Aug 2002 15:52:50 -0400 [thread overview]
Message-ID: <3D52CC12.9090909@mandrakesoft.com> (raw)
Since Linus does not do pre-patches anymore, he mentioned some time ago
it would be nice if somebody created an automated BK snapshot process to
make BK changes accessible between kernel releases. I've done that.
ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/snap/2.5/
All BK changes not in the current 2.5 kernel release will be posted at
this URL, in GNU patch form, on a daily basis. [snap happens at one
minute past midnight, California time] The full changelog log is also
extracted. Each time Linus releases a new kernel, the contents of this
directory will be wiped out.
Questions and comments welcome.
Jeff
next reply other threads:[~2002-08-08 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 19:52 Jeff Garzik [this message]
2002-08-08 19:55 ` Announce: daily 2.5 BK snapshots Jeff Garzik
2002-08-08 20:04 ` Rik van Riel
2002-08-08 20:17 ` Jeff Garzik
2002-08-09 14:36 ` Paul Larson
2002-08-09 14:55 ` Larry McVoy
2002-08-09 15:19 ` Martin J. Bligh
2002-08-09 15:49 ` Larry McVoy
2002-08-09 19:03 ` Paul Larson
[not found] ` <200208082127.OAA08172@cesium.transmeta.com>
2002-08-08 21:34 ` Jeff Garzik
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=3D52CC12.9090909@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.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