Xen devel - Jun 2007 - xenbits xen-unstable.hg repo time-travelling?

I''ve just noticed that the xen-unstable repo at
http://xenbits.xensource.com/xen-unstable.hg has its tip at
15080:89696e0c603. Last time I pulled I got 15190:c9d66baad22b, so it
seems the public repo has rolled back 110 changesets. Was this by
accident or design?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Are you sure you didn''t pull from the staging tree or some descendent
of it?
The ''main'' tree is certainly many many changesets behind, but
I don''t think
those have been pushed and reverted; they simply haven''t pushed at all
because of failing regression tests.

 -- Keir

On 2/6/07 00:07, "Brendan Cully" <brendan@cs.ubc.ca> wrote:
> I''ve just noticed that the xen-unstable repo at
> http://xenbits.xensource.com/xen-unstable.hg has its tip at
> 15080:89696e0c603. Last time I pulled I got 15190:c9d66baad22b, so it
> seems the public repo has rolled back 110 changesets. Was this by
> accident or design?
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Saturday, 02 June 2007 at 11:15, Keir Fraser wrote:
> Are you sure you didn''t pull from the staging tree or some
descendent of it?
> The ''main'' tree is certainly many many changesets behind,
but I don''t think
> those have been pushed and reverted; they simply haven''t pushed at
all
> because of failing regression tests.
I guess it''s possible. I noticed it in a local mirror that just runs
hg pull via cron once an hour, so I''m not sure how I might have pulled
staging. But it''s probably not worth investigating.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel