pkasting@chromium.org 16825b1a82 Use int64_t more consistently for times, in particular for RTT values. ... Existing code was inconsistent about whether to use uint16_t, int, unsigned int, or uint32_t, and sometimes silently truncated one to another, or truncated int64_t. Because most core time-handling functions use int64_t, being consistent about using int64_t unless otherwise necessary minimizes the number of explicit or implicit casts. BUG=chromium:81439 TEST=none R=henrik.lundin@webrtc.org, holmer@google.com, tommi@webrtc.org Review URL: https://webrtc-codereview.appspot.com/31349004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@8045 4adac7df-926f-26a2-2b94-8c16560cd09d		2015-01-12 21:51:21 +00:00
..
base	Use int64_t more consistently for times, in particular for RTT values.	2015-01-12 21:51:21 +00:00
devices	Hard define the GUID for AudioEndpoint to avoid conflicts during compile.	2015-01-08 19:18:01 +00:00
other	(Auto)update libjingle 77263371-> 77296420	2014-10-08 22:24:30 +00:00
sctp	(Auto)update libjingle 77263371-> 77296420	2014-10-08 22:24:30 +00:00
testdata	* Move test data assests required by video frame tests to be in libjingle instead of elsewhere and co-located with other libjingle test data files.	2014-09-03 23:17:36 +00:00
webrtc	Use int64_t more consistently for times, in particular for RTT values.	2015-01-12 21:51:21 +00:00