From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Announce: daily 2.5 BK snapshots
Date: Thu, 08 Aug 2002 16:17:13 -0400 [thread overview]
Message-ID: <3D52D1C9.9070404@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.44L.0208081703260.2589-100000@duckman.distro.conectiva
Rik van Riel wrote:
> On Thu, 8 Aug 2002, Jeff Garzik wrote:
>
>
>>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/
>
>
>>Questions and comments welcome.
>
>
> Heh, I've had something vaguely like this on NL.linux.org:
>
> ftp://ftp.nl.linux.org/pub/linux/bk2patch/
>
> Every 3 hours it creates a unidiff between the latest
> tagged version and the head of the bk tree, for both 2.5
> and 2.4.
Just to forestall other private responses [already gotten two], mine is
slightly different than your's, and David Woodhouse's setup. My goal
was basically to create a daily pre-patch, complete with hacked
EXTRAVERSION. That's something that is familiar to testers (pre-patch
form), and the snapshot is not so often that people will get buried in a
flurry of patches and csets. can you say "2.5.30-bk439" ;-)
So I consider my dailies as a complement to your bk2patch and dwmw2's
output, not redundant. Programmers would probably find dwmw2's per-cset
patches to be more useful, while testers and power users, and maybe
maintainers, would prefer daily pre-patches to test and sync against.
Jeff
next prev parent reply other threads:[~2002-08-08 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 19:52 Announce: daily 2.5 BK snapshots Jeff Garzik
2002-08-08 19:55 ` Jeff Garzik
2002-08-08 20:04 ` Rik van Riel
2002-08-08 20:17 ` Jeff Garzik [this message]
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=3D52D1C9.9070404@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.