All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: nightly snapshots have 2.6.11 sparse tree
Date: Wed, 13 Jul 2005 17:31:22 +0200	[thread overview]
Message-ID: <20050713153122.GA12395@snarc.org> (raw)
In-Reply-To: <20050713151656.GB28623@us.ibm.com>

On Wed, Jul 13, 2005 at 10:16:56AM -0500, Ryan Harper wrote:
> It seems that the nightly [1]snapshots still have the [2]2.6.11 sparse tree.
> Is this intended?  I thought unstable branch switched over to 2.6.12 a
> few days ago?

There's a problem with the nightly snapshot which contains an old
version of the tree.

you can still update with mercurial for the moment.

> 2. 
> % tar tzvf xen-unstable-src.tgz xen-unstable/linux-2.6.11-xen-sparse  | wc -l
> 289
> % tar tzvf xen-unstable-src.tgz xen-unstable/linux-2.6.12-xen-sparse  | wc -l
> 0

anyhow, the sparse tree has been renamed to linux-2.6-xen-sparse

-- 
Vincent Hanquez

  reply	other threads:[~2005-07-13 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 15:16 nightly snapshots have 2.6.11 sparse tree Ryan Harper
2005-07-13 15:31 ` Vincent Hanquez [this message]
2005-07-13 15:35   ` Ryan Harper

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=20050713153122.GA12395@snarc.org \
    --to=vincent.hanquez@cl.cam.ac.uk \
    --cc=ryanh@us.ibm.com \
    --cc=xen-devel@lists.xensource.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 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.