From a80c8f6887aa6cb92d783bb701f17dd86f9f15d4 Mon Sep 17 00:00:00 2001 From: Thomas Vander Stichele Date: Thu, 2 Feb 2006 08:47:42 +0000 Subject: [PATCH] reformat to fit 80 chars Original commit message from CVS: reformat to fit 80 chars --- common | 2 +- tests/check/pipelines/theoraenc.c | 30 +++++++++++++++--------------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/common b/common index 0b93085188..1140eabed8 160000 --- a/common +++ b/common @@ -1 +1 @@ -Subproject commit 0b93085188e83fe678ec5ded2823cd7c24dfa843 +Subproject commit 1140eabed84dd1d8d6df7df88f5c8bdf20a8faa1 diff --git a/tests/check/pipelines/theoraenc.c b/tests/check/pipelines/theoraenc.c index cfdb018e1b..c5ed7be737 100644 --- a/tests/check/pipelines/theoraenc.c +++ b/tests/check/pipelines/theoraenc.c @@ -136,11 +136,11 @@ check_buffer_granulepos (GstBuffer * buffer, GstClockTime granulepos) granulepos, GST_BUFFER_OFFSET_END (buffer)); } -/* this check is here to check that the granulepos we derive from the timestamp - is about correct. This is "about correct" because you can't precisely go from - timestamp to granulepos due to the downward-rounding characteristics of - gst_util_uint64_scale, so you check if granulepos is equal to the number, or - the number plus one. */ +/* this check is here to check that the granulepos we derive from the + timestamp is about correct. This is "about correct" because you can't + precisely go from timestamp to granulepos due to the downward-rounding + characteristics of gst_util_uint64_scale, so you check if granulepos is + equal to the number, or the number plus one. */ /* should be from_endtime, but theora's granulepos mapping is "special" */ static void check_buffer_granulepos_from_starttime (GstBuffer * buffer, @@ -214,10 +214,10 @@ GST_START_TEST (test_granulepos_offset) /* first buffer should have timestamp of TIMESTAMP_OFFSET, granulepos to * match the timestamp of the end of the last sample in the output buffer. - * Note that one cannot go timestamp->granulepos->timestamp and get the same - * value due to loss of precision with granulepos. theoraenc does take care - * to timestamp correctly based on the offset of the input data however, so - * it does do sub-granulepos timestamping. */ + * Note that one cannot go timestamp->granulepos->timestamp and get the + * same value due to loss of precision with granulepos. theoraenc does + * take care to timestamp correctly based on the offset of the input data + * however, so it does do sub-granulepos timestamping. */ buffer = get_buffer (bin, pad); last_granulepos = GST_BUFFER_OFFSET_END (buffer); check_buffer_timestamp (buffer, TIMESTAMP_OFFSET); @@ -302,15 +302,15 @@ GST_START_TEST (test_continuity) /* first buffer should have timestamp of TIMESTAMP_OFFSET, granulepos to * match the timestamp of the end of the last sample in the output buffer. - * Note that one cannot go timestamp->granulepos->timestamp and get the same - * value due to loss of precision with granulepos. theoraenc does take care - * to timestamp correctly based on the offset of the input data however, so - * it does do sub-granulepos timestamping. */ + * Note that one cannot go timestamp->granulepos->timestamp and get the + * same value due to loss of precision with granulepos. theoraenc does + * take care to timestamp correctly based on the offset of the input data + * however, so it does do sub-granulepos timestamping. */ buffer = get_buffer (bin, pad); last_granulepos = GST_BUFFER_OFFSET_END (buffer); check_buffer_timestamp (buffer, 0); - check_buffer_duration (buffer, GST_SECOND / 10); /* plain division because I - know the answer is exact */ + /* plain division because I know the answer is exact */ + check_buffer_duration (buffer, GST_SECOND / 10); check_buffer_granulepos (buffer, 0); next_timestamp = GST_BUFFER_DURATION (buffer); -- 2.34.1