<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: De-tangling timestamps: part2</title>
	<atom:link href="http://oduinn.com/blog/2008/06/26/de-tangling-timestamps-part2/feed/" rel="self" type="application/rss+xml" />
	<link>http://oduinn.com/blog/2008/06/26/de-tangling-timestamps-part2/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 24 Aug 2010 20:19:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: John O&#8217;Duinn&#8217;s Soapbox &#187; De-tangling timestamps: part3 - the new BuildID!</title>
		<link>http://oduinn.com/blog/2008/06/26/de-tangling-timestamps-part2/#comment-8741</link>
		<dc:creator>John O&#8217;Duinn&#8217;s Soapbox &#187; De-tangling timestamps: part3 - the new BuildID!</dc:creator>
		<pubDate>Fri, 08 Aug 2008 08:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2008/06/26/de-tangling-timestamps-part2/#comment-8741</guid>
		<description>[...] the Tinderbox, Builds, Unittest, Talos and GraphServer systems all needed ways to uniquely identify builds, so each system invented their own (different!) way of doing this&#8230; all because the old BuildID was not good enough. Matching up these different systems - how to post a talos result on tinderbox for example - is quite a headache. We&#8217;ve already done some cleanup (here and here), but this new BuildID should let us simplify *much* more of that cross-system integration. [...]</description>
		<content:encoded><![CDATA[<p>[...] the Tinderbox, Builds, Unittest, Talos and GraphServer systems all needed ways to uniquely identify builds, so each system invented their own (different!) way of doing this&#8230; all because the old BuildID was not good enough. Matching up these different systems &#8211; how to post a talos result on tinderbox for example &#8211; is quite a headache. We&#8217;ve already done some cleanup (here and here), but this new BuildID should let us simplify *much* more of that cross-system integration. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
