Revisions: Re-think the way how the current revision is detected
|Reported by:||ocean90||Owned by:||nacin|
|Severity:||normal||Keywords:||has-patch commit 2nd-opinion|
|Cc:||adamsilverstein, markjaquith, a.hoereth@…|
This can be an issue if you are using the API and creating revisions programmatically which can result in same timestamps, since we doesn't save milliseconds, only seconds.
Not sure if we can do something here, but want to make it known.
Change History (9)
- Keywords has-patch added
- Milestone changed from Awaiting Review to 3.6
- Version set to trunk
- Owner set to nacin
- Resolution set to fixed
- Status changed from new to closed
Note: See TracTickets for help on using tickets.