From: Jacek Kawa <jfk@zeus.polsl.gliwice.pl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Update to 2.5.x snapshots
Date: Sat, 1 Mar 2003 23:29:10 +0100 [thread overview]
Message-ID: <20030301222910.GA3983@finwe.eu.org> (raw)
In-Reply-To: <3E612A27.2050200@pobox.com>
Jeff Garzik wrote:
> >>Old 2.5.x BK snapshots on kernel.org are now moved into the "old"
> >>sub-directory, instead of being deleted.
[...]
> >It may not be related, but
> >http://www.kernel.org/pub/linux/kernel/v2.4/testing/cset/
> >has "BitKeeper patches since v2.4.21-pre4: 354 Changesets"
> >(not latest -pre).
> Yep, I know :)
> The point of nightly snapshots is more for users use and testing
> purposes. The csets are very useful for developers, but a bit of a
> moving target for users.
I'm just used to look there from time to time to see 'what is new', and
AFAIR changes were reported against latest prerelease.
>From my point of view, as long as patches are in chronological order
it's not a problem. :)
> If users are using the per-cset snapshots,
> then it becomes a non-trivial chore to developers to track down exactly
> what version of the kernel a problem is reported against.
Csets are useful for users- e.g. if the problem you want to report does
not exist in latest cset -but generaly you are right.
Jacek
prev parent reply other threads:[~2003-03-01 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 18:23 Update to 2.5.x snapshots Jeff Garzik
2003-03-01 21:16 ` Jacek Kawa
2003-03-01 21:46 ` Jeff Garzik
2003-03-01 22:29 ` Jacek Kawa [this message]
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=20030301222910.GA3983@finwe.eu.org \
--to=jfk@zeus.polsl.gliwice.pl \
--cc=jgarzik@pobox.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 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.