Hi Michael, *;

On Mon, Aug 24, 2009 at 2:42 PM, Michael Stahl<[email protected]> wrote:
> Christian Lohmaier wrote:
>> [getting a list of changes since $date/$revision for use with tinderbox]
>
> tinderbox is from mozilla, right?

Yes, it originates from mozilla.

> iirc, mozilla switched to hg some time ago.
> so i would assume they have some kind of solution for this problem.
> have you investigated what they are doing?

Apparently they are not using change tracking in tinderbox
anymore/only used it with cvs projects (via bonsai).
see e.g. http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox3.6

Their bots build so often, so that it doesn't matter. It doesn't
matter to them either that different "alias" bots build the exact same
revision. OOo project doesn't have that many tinderboxes yet :-)

However, mozilla's hg webserver has this:

http://hg.mozilla.org/releases/mozilla-1.9.2/pushloghtml
Yay - a from-to entry that accepts dates! and the feed-version
(without the "html" to the URL provides an atom-feed that lists the
affected files instead of the comments (strangely enough - why
comments on the html, and files (but no comment) in the feed? Hmm....)

http://hg.mozilla.org/releases/mozilla-1.9.2/pushloghtml?startdate=2009-08-20&enddate=now
and that also works for the feed:
http://hg.mozilla.org/releases/mozilla-1.9.2/pushlog?startdate=2009-08-20&enddate=now

Unfortunately, this is not available on OOo's version :-/

> if all else fails, then you could probably get by with a single local
> repository, into which you pull all cws repositories. hopefully, the pull
> should indicate whether it actually pulled something, and if it did, it
> will be the "tip" in the local repository. this would not be horribly
> slow, because you only pull the large changes that are common in all cws
> (from rebase) _once_.

So after a pull of a cws, that will always be the new tip?

ciao
Christian

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to