From: Brian Gerst <bgerst@didntduck.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: BK snapshots broken
Date: Wed, 16 Mar 2005 09:53:51 -0500 [thread overview]
Message-ID: <4238487F.5050708@didntduck.org> (raw)
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.
--
Brian Gerst
next reply other threads:[~2005-03-16 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 14:53 Brian Gerst [this message]
2005-03-16 16:06 ` BK snapshots broken Prakash Punnoor
2005-03-16 18:31 ` 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=4238487F.5050708@didntduck.org \
--to=bgerst@didntduck.org \
--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