public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: sean <seandarcy2@gmail.com>,
	linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: BK snapshots removed from kernel.org?
Date: Wed, 30 Mar 2005 22:58:59 -0500	[thread overview]
Message-ID: <20050331035859.GA23124@redhat.com> (raw)
In-Reply-To: <424B72CC.8030801@osdl.org>

On Wed, Mar 30, 2005 at 07:47:24PM -0800, Randy.Dunlap wrote:
 > sean wrote:
 > >Randy.Dunlap wrote:
 > >
 > >>
 > >>Did you look in
 > >>http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/old/ ?
 > >>
 > >
 > >Yes I did.
 > >
 > >Latest is 2.6.12-rc1-bk2, March 26.
 > >
 > >None since then?
 > 
 > I can't explain it other than "the snapshots are broken."
 > All I do is look around for them, and behold, just look in
 > 
 > http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/
 > 
 > for the 2.6.11.6-bk snapshots.

This madness ensues each time Linus pulls GregKH's tree
into his. The script stops snapshotting against Linus'
tree, and opts to produce -bk's against GregKH's for
some bizarre reason.

		Dave


  reply	other threads:[~2005-03-31  3:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 17:14 BK snapshots removed from kernel.org? Norberto Bensa
2005-03-27 21:02 ` Barry K. Nathan
2005-03-28 15:26   ` Norberto Bensa
2005-03-28 15:40     ` Randy.Dunlap
2005-03-28 17:19       ` Norberto Bensa
2005-03-31  3:34       ` sean
2005-03-31  3:47         ` Randy.Dunlap
2005-03-31  3:58           ` Dave Jones [this message]
2005-03-31  4:17           ` Jeff Garzik
2005-03-31  4:29             ` Dave Jones
2005-03-31  4:44               ` Jeff Garzik
2005-03-31  6:02             ` Greg KH
2005-03-31 11:42               ` Prakash Punnoor
2005-03-31 20:25                 ` Greg KH

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=20050331035859.GA23124@redhat.com \
    --to=davej@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=seandarcy2@gmail.com \
    /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