From: James Bulpin <james@xensource.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, David_Wolinsky@Dell.com
Subject: Re: What happened?
Date: Sun, 17 Jul 2005 21:11:01 +0100 [thread overview]
Message-ID: <42DABB55.1040609@xensource.com> (raw)
In-Reply-To: <1af99535c1228390ecb449677631b1ea@cl.cam.ac.uk>
The other thing to watch out for is the history (hg history and web
interface) is ordered by the date the changeset was applied to the
repository in question rather than when it was first checked into a
repository (the latter being the date field in the history). Changesets
5792 to 5804 were made to the IA64 tree a while ago. They were merged
with the main tree on Friday which is why you see a break in the date
ordering.
James
Keir Fraser wrote:
>
> On 17 Jul 2005, at 14:33, <David_Wolinsky@Dell.com> wrote:
>
>> What happened to xenbits… After change set 5792, it seems to be time
>> retarded… what's the possibility of something like this breaking Xen?
>> I ask, because I had a stable system and now its back to the state is
>> was a week ago… (I am only sshed in so I can't give more detailed info).
>
>
> There doesn't appear to be anything wrong with xenbits. I just cloned a
> fresh copy of it and it looks up to date.
>
> If you pull new changesets into an existing local repository, you do
> need to 'hg update' to make your check-out copy match the latest version.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-07-17 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 13:33 What happened? David_Wolinsky
2005-07-17 13:40 ` Keir Fraser
2005-07-17 20:11 ` James Bulpin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-17 20:58 David_Wolinsky
2005-07-18 7:43 ` Keir Fraser
2005-07-18 14:45 David_Wolinsky
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=42DABB55.1040609@xensource.com \
--to=james@xensource.com \
--cc=David_Wolinsky@Dell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.