public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: BK snapshots broken
Date: Wed, 16 Mar 2005 13:31:37 -0500	[thread overview]
Message-ID: <42387B89.8@pobox.com> (raw)
In-Reply-To: <4238487F.5050708@didntduck.org>

Brian Gerst wrote:
> The snapshots on kernel.org are being created from the most recent tag 
> in the BK repo, which is 2.6.11.3.  That means they are missing all of 
> the changesets between the 2.6.11 and 2.6.11.3 tags, and don't apply to 
> a clean 2.6.11 tree.

This is my fault, but I won't have a chance to fix for a day or two.

The BK snapshot script finds the latest kernel version by looking at the 
BK tag.  It should probably look directly at the Makefile, I suppose.

	Jeff



      parent reply	other threads:[~2005-03-16 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 14:53 BK snapshots broken Brian Gerst
2005-03-16 16:06 ` Prakash Punnoor
2005-03-16 18:31 ` Jeff Garzik [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=42387B89.8@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bgerst@didntduck.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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