| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| README.timetable | 2015-02-12 | 519 Bytes | |
| cutmts-1.0-2.i386.rpm | 2015-02-12 | 12.4 kB | |
| cutmts-1.0.tar.bz2 | 2015-02-12 | 20.6 kB | |
| cutmts_1.0-1_i386.deb | 2015-02-12 | 10.6 kB | |
| Changelog | 2015-02-12 | 27 Bytes | |
| USAGE | 2015-02-12 | 1.9 kB | |
| README | 2015-02-12 | 816 Bytes | |
| Totals: 7 Items | 47.0 kB | 1 |
NOTE: The options -a and -b override a given timetable A timetable should look like this, the format is always: startpoint endpoint startpoint endpoint like: ---- 8< cut here ---- 0:01 1:00 1:05 3:57 11:15 19:33 01:01.34 02:39.78 0:0 -1:0 ---- 8< cut here ---- Without ':' numbers only mean minutes, but 3.7 means 3.7 seconds Negative time means distance from end of file. Syntax is NOT hh:mm:ss but mm:ss.subseconds So writing a timetable should not be difficult, just use your common sense ;-)