This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 167083 - Strange time/date sorting in hgweb
Summary: Strange time/date sorting in hgweb
Status: RESOLVED INVALID
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-15 09:08 UTC by _ tboudreau
Modified: 2009-06-16 17:27 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screen shot (113.98 KB, image/png)
2009-06-15 09:08 UTC, _ tboudreau
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2009-06-15 09:08:06 UTC
Probably actually an hgwebdir or hgweb bug:  Look at the attached screen shot.  It is showing commits in order - Jarda's
commits were later than mine.  

But Jarda's newer commits show up as "23 hours ago" while mine (really 12 hours ago) say "12 hours ago".  Maybe some
javascript is converting GMT to local time on the client when the page is generated or something?  The order is right,
but the time values make no sense.
Comment 1 _ tboudreau 2009-06-15 09:08:48 UTC
Created attachment 83569 [details]
screen shot
Comment 2 _ tboudreau 2009-06-15 09:11:10 UTC
Or maybe this is an artifact of how our semi-incomprehensible system of build repositories merges itself together, and
Jarda's work is really older?
Comment 3 Jesse Glick 2009-06-16 17:27:04 UTC
hgweb{,dir} does not sort changesets by commit date; commit date is basically informational, like author or description
(in fact you can freely specify an alternate date when committing, using -d). They are sorted by the order in which they
arrived in (this clone of) the repository. In Mercurial, like in any DVCS, changesets can be partially ordered but not
totally ordered, so any linear list of changesets has to impose an artificial ordering; the "true" view would be a DAG,
but this is hard to pack into a readable web page.