1998/freebsd-current/19980215.freebsd-current
Messages: 294, sorted by subject
|
Last update: Mon Feb 13 14:14:58 UTC 2023
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Feb 21 =?koi8-r?B?4c7E0sXKIP7F0s7 "calcru: negative time ..." for adjkerntz 2. Feb 19 Adam McDougall -current breakage as of 8:30am EST Thursday 3. Feb 19 Eivind Eklund Re: -current breakage as of 8:30am EST Thursday 4. Feb 19 Adam McDougall Re: -current breakage as of 8:30am EST Thursday 5. Feb 15 Terry Lambert Re: about my last panic 6. Feb 16 Dmitrij Tejblum Re: about my last panic 7. Feb 21 Brian Tao Bogus VSZ output in `ps' 8. Feb 21 John S. Dyson Re: Bogus VSZ output in `ps' 9. Feb 21 John Fieber Re: Bogus VSZ output in `ps' 10. Feb 21 John S. Dyson Re: Bogus VSZ output in `ps' 11. Feb 21 John S. Dyson Re: Bogus VSZ output in `ps' 12. Feb 15 freebsd@isvara.net Re: boot.flp bug? 13. Feb 19 osa@unibest.ru Cann't compile new kernel.... 14. Feb 19 Eivind Eklund Re: Cann't compile new kernel.... 15. Feb 15 Jordan K. Hubbard Re: CCD missing spl() call.. 16. Feb 15 Jordan K. Hubbard Re: CCD missing spl() call.. 17. Feb 15 Greg Lehey Re: CCD missing spl() call.. 18. Feb 15 Jordan K. Hubbard Re: CCD missing spl() call.. 19. Feb 15 Chris Csanady Re: CCD missing spl() call.. 20. Feb 15 Greg Lehey Re: CCD missing spl() call..
21. Feb 15 Jordan K. Hubbard Re: CCD missing spl() call.. 22. Feb 15 Greg Lehey Re: CCD missing spl() call.. 23. Feb 15 Terry Lambert Re: CCD missing spl() call.. 24. Feb 15 Jordan K. Hubbard Re: CCD missing spl() call.. 25. Feb 16 Pierre Beyssac Re: CCD missing spl() call.. 26. Feb 16 daniel_sobral@voga.com.br Re: CCD missing spl() call.. 27. Feb 21 Ron Bolin Current Builds but Make installworld bombs 28. Feb 17 Penisoara Adrian Re: Current dying horribly when using lp0 29. Feb 21 Amancio Hasty Current is broken with latest builds..., blah, blah. 30. Feb 21 Terry Lambert Re: Current is broken with latest builds..., blah, blah. 31. Feb 21 Amancio Hasty Re: Current is broken with latest builds..., blah, blah. 32. Feb 20 Ron Bolin Current is still broken 33. Feb 21 Eivind Eklund Re: Current is still broken 34. Feb 21 Greg Lehey Re: Current is still broken 35. Feb 21 Eivind Eklund Re: Current is still broken 36. Feb 17 Peter Mutsaers Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 37. Feb 17 Eivind Eklund Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 38. Feb 17 Eivind Eklund Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 39. Feb 17 Luigi Rizzo Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 40. Feb 17 Garrett Wollman Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v
41. Feb 17 Eivind Eklund Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 42. Feb 17 Luigi Rizzo Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 43. Feb 18 Luigi Rizzo Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h v 44. Feb 17 Brian Somers Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h vars.c var 45. Feb 17 Brian Somers Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h vars.c var 46. Feb 17 Brian Somers Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h vars.c var 47. Feb 17 Eivind Eklund Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h vars.c var 48. Feb 18 Luigi Rizzo Re: cvs commit: src/usr.sbin/ppp command.c datalink.c datalink.h defs.h vars.c var 49. Feb 16 Julian Elischer Re: devfs persistence 50. Feb 16 Julian Elischer Re: devfs persistence 51. Feb 16 Nate Williams Re: devfs persistence 52. Feb 16 Terry Lambert Re: devfs persistence 53. Feb 16 Terry Lambert Re: devfs persistence 54. Feb 16 Simon Shapiro Re: devfs persistence 55. Feb 16 Archie Cobbs Re: devfs persistence 56. Feb 16 sthaug@nethelp.no Re: devfs persistence 57. Feb 17 Terry Lambert Re: devfs persistence 58. Feb 17 Mike Smith Re: devfs persistence 59. Feb 17 Zach Heilig Re: devfs persistence 60. Feb 17 Julian Elischer Re: devfs persistence
61. Feb 17 Simon Shapiro Re: devfs persistence 62. Feb 17 Julian Elischer Re: devfs persistence 63. Feb 17 Simon Shapiro Re: devfs persistence 64. Feb 17 sthaug@nethelp.no Re: devfs persistence 65. Feb 17 Poul-Henning Kamp Re: devfs persistence 66. Feb 17 Mike Smith Re: devfs persistence 67. Feb 17 Terry Lambert Re: devfs persistence 68. Feb 18 David Dawes Re: devfs persistence 69. Feb 21 Justin T. Gibbs Re: devfs persistence 70. Feb 21 Justin T. Gibbs Re: devfs persistence 71. Feb 21 Terry Lambert Re: devfs persistence 72. Feb 21 Justin T. Gibbs Re: devfs persistence 73. Feb 21 Terry Lambert Re: devfs persistence 74. Feb 21 Justin T. Gibbs Re: devfs persistence 75. Feb 21 Terry Lambert Re: devfs persistence 76. Feb 21 Julian Elischer Re: devfs persistence 77. Feb 19 Kevin Lam Fatal Trap 18: integer divide fault 78. Feb 19 Goeringer, Michael Finding MGR 79. Feb 19 Andrzej Bialecki Re: Finding MGR 80. Feb 17 Simon Shapiro FW: Re: devfs persistence
81. Feb 17 Axel Thimm Re: getcwd, fork & vfork 82. Feb 20 dannyman gimp under -current? 83. Feb 20 Alex Re: gimp under -current? 84. Feb 20 Robert Watson Re: gimp under -current? 85. Feb 20 dannyman Re: gimp under -current? 86. Feb 20 Alex Re: gimp under -current? 87. Feb 20 dannyman Re: gimp under -current? 88. Feb 20 Edwin Culp Re: gimp under -current? 89. Feb 20 dannyman Re: gimp under -current? 90. Feb 21 brian@worldcontrol.com Re: gimp under -current? 91. Feb 21 dannyman Re: gimp under -current? 92. Feb 19 Terry Lambert Re: Heads up: src/games/boggle (tm) will soon be removed from 93. Feb 19 Richard Wackerbarth Re: Heads up: src/games/boggle (tm) will soon be removed from 94. Feb 19 Terry Lambert Re: Heads up: src/games/boggle (tm) will soon be removed from 95. Feb 19 Jordan K. Hubbard Re: Heads up: src/games/boggle (tm) will soon be removed from 96. Feb 19 Richard Wackerbarth Re: Heads up: src/games/boggle (tm) will soon be removed from 97. Feb 18 Amancio Hasty Re: Heads up: src/games/boggle (tm) will soon be removed from repository 98. Feb 18 John Polstra Heads up: src/games/boggle (tm) will soon be removed from repository 99. Feb 18 Terry Lambert Re: Heads up: src/games/boggle (tm) will soon be removed from repository 100. Feb 18 John Polstra Re: Heads up: src/games/boggle (tm) will soon be removed from repository
101. Feb 18 Jordan K. Hubbard Re: Heads up: src/games/boggle (tm) will soon be removed from repository 102. Feb 18 Julian Elischer Re: Heads up: src/games/boggle (tm) will soon be removed from repository 103. Feb 18 Nate Williams Re: Heads up: src/games/boggle (tm) will soon be removed from repository 104. Feb 19 Terry Lambert Re: Heads up: src/games/boggle (tm) will soon be removed from repository 105. Feb 19 Terry Lambert Re: Heads up: src/games/boggle (tm) will soon be removed from repository 106. Feb 19 Terry Lambert Re: Heads up: src/games/boggle (tm) will soon be removed from repository 107. Feb 20 John S. Dyson I'm Back!!! 108. Feb 15 Steve Logue Jaz Drives / Tagged Command Queuing 109. Feb 15 brian@worldcontrol.com Re: Jaz Drives / Tagged Command Queuing 110. Feb 17 Michael Bielicki KDE Beta 3.1 PORT not compileable 111. Feb 17 Satoshi Asami Re: KDE Beta 3.1 PORT not compileable 112. Feb 17 Michael.Bielicki@linkdesig Re: KDE Beta 3.1 PORT not compileable 113. Feb 16 Kingson Gunawan kernel panic on smp system 114. Feb 20 Greg Lehey Latest -current make world breakage 115. Feb 20 John Birrell Re: Latest -current make world breakage 116. Feb 15 Amancio Hasty Latest -current panic 8) 117. Feb 21 dannyman make buildworld dies here too! 118. Feb 21 dannyman Re: make buildworld dies here too! 119. Feb 20 Gianmarco Giovannelli Make World fails : cvsup 980219 120. Feb 20 Greg Lehey Re: Make World fails : cvsup 980219
121. Feb 20 Eivind Eklund Re: Make World fails : cvsup 980219 122. Feb 20 Greg Lehey Re: Make World fails : cvsup 980219 123. Feb 20 Werner Griessl Re: Make World fails : cvsup 980219 124. Feb 20 Adam McDougall Re: Make World fails : cvsup 980219 125. Feb 16 Joakim Henriksson Memory report problems. 126. Feb 16 Jason Young Re: Memory report problems. 127. Feb 16 Joakim Henriksson Re: Memory report problems. 128. Feb 16 Greg Lehey Re: Memory report problems. 129. Feb 16 Joakim Henriksson Re: Memory report problems. 130. Feb 16 Greg Lehey Re: Memory report problems. 131. Feb 16 Greg Lehey Re: Memory report problems. 132. Feb 18 Andrzej Bialecki MGR and libvgl 133. Feb 18 Søren Schmidt Re: MGR and libvgl 134. Feb 18 Philippe Regnauld Re: MGR and libvgl 135. Feb 18 Mike Smith Re: MGR and libvgl 136. Feb 18 Jordan K. Hubbard Re: MGR and libvgl 137. Feb 18 Philippe Regnauld Re: MGR and libvgl 138. Feb 18 Andrzej Bialecki Re: MGR and libvgl 139. Feb 18 Andrzej Bialecki Re: MGR and libvgl 140. Feb 18 Søren Schmidt Re: MGR and libvgl
141. Feb 19 Terry Lambert Re: MGR and libvgl 142. Feb 19 Jordan K. Hubbard Re: MGR and libvgl 143. Feb 19 Jonathan Mini Re: MGR and libvgl 144. Feb 19 Pedro F. Giffuni Re: MGR and libvgl 145. Feb 19 Andrzej Bialecki Re: MGR and libvgl 146. Feb 19 Tom Re: MGR and libvgl 147. Feb 19 Jonathan Mini Re: MGR and libvgl 148. Feb 19 Jonathan Mini Re: MGR and libvgl 149. Feb 19 Daniel O'Connor Re: MGR and libvgl 150. Feb 19 Jonathan Mini Re: MGR and libvgl 151. Feb 19 Scott Michel Re: MGR and libvgl 152. Feb 19 Daniel O'Connor Re: MGR and libvgl 153. Feb 20 Keith Marshall Re: MGR and libvgl 154. Feb 20 Andrzej Bialecki MGR and the like... 155. Feb 21 Goeringer, Michael RE: MGR and the like... 156. Feb 20 Jordan K. Hubbard More breakage in -current as a result of header frobbing. 157. Feb 20 Jordan K. Hubbard Re: More breakage in -current as a result of header frobbing. 158. Feb 20 John Birrell Re: More breakage in -current as a result of header frobbing. 159. Feb 20 Jordan K. Hubbard Re: More breakage in -current as a result of header frobbing. 160. Feb 20 Sean Eric Fagan Re: More breakage in -current as a result of header frobbing.
161. Feb 20 Terry Lambert Re: More breakage in -current as a result of header frobbing. 162. Feb 20 Greg Lehey Re: More breakage in -current as a result of header frobbing. 163. Feb 20 Scott Michel Re: More breakage in -current as a result of header frobbing. 164. Feb 20 Greg Lehey Re: More breakage in -current as a result of header frobbing. 165. Feb 20 John S. Dyson Re: More breakage in -current as a result of header frobbing. 166. Feb 20 Alfred Perlstein Re: More breakage in -current as a result of header frobbing. 167. Feb 21 Jordan K. Hubbard Re: More breakage in -current as a result of header frobbing. 168. Feb 21 Eivind Eklund Re: More breakage in -current as a result of header frobbing. 169. Feb 21 Jordan K. Hubbard Re: More breakage in -current as a result of header frobbing. 170. Feb 21 John Birrell Re: More breakage in -current as a result of header frobbing. 171. Feb 21 Richard Wackerbarth Re: More breakage in -current as a result of header frobbing. 172. Feb 21 Chris Timmons Re: More breakage in -current as a result of header frobbing. 173. Feb 21 John S. Dyson Re: More breakage in -current as a result of header frobbing. 174. Feb 21 Nate Williams Re: More breakage in -current as a result of header frobbing. 175. Feb 21 John Kelly Re: More breakage in -current as a result of header frobbing. 176. Feb 21 Richard Wackerbarth Re: More breakage in -current as a result of header frobbing. 177. Feb 21 Jordan K. Hubbard Re: More breakage in -current as a result of header frobbing. 178. Feb 21 Amancio Hasty Re: More breakage in -current as a result of header frobbing. 179. Feb 21 Brian Handy Re: More breakage in -current as a result of header frobbing. 180. Feb 21 Terry Lambert Re: More breakage in -current as a result of header frobbing.
181. Feb 21 Terry Lambert Re: More breakage in -current as a result of header frobbing. 182. Feb 21 Greg Lehey Re: More breakage in -current as a result of header frobbing. 183. Feb 21 Nate Williams Re: More breakage in -current as a result of header frobbing. 184. Feb 21 Warner Losh Re: More breakage in -current as a result of header frobbing. 185. Feb 21 Terry Lambert Re: More breakage in -current as a result of header frobbing. 186. Feb 21 Warner Losh Re: More breakage in -current as a result of header frobbing. 187. Feb 21 Nate Williams Re: More breakage in -current as a result of header frobbing. 188. Feb 21 Jordan K. Hubbard Re: More breakage in -current as a result of header frobbing. 189. Feb 18 Jordan K. Hubbard New 3.0 SNAPshot CDROM about ready for production.. 190. Feb 18 Satoshi Asami Re: New 3.0 SNAPshot CDROM about ready for production.. 191. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production.. 192. Feb 18 Andrzej Bialecki Re: New 3.0 SNAPshot CDROM about ready for production.. 193. Feb 18 Mike Smith Re: New 3.0 SNAPshot CDROM about ready for production.. 194. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production.. 195. Feb 18 John S. Dyson Re: New 3.0 SNAPshot CDROM about ready for production.. 196. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production.. 197. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production.. 198. Feb 18 Greg Lehey Re: New 3.0 SNAPshot CDROM about ready for production.. 199. Feb 18 John Kelly Re: New 3.0 SNAPshot CDROM about ready for production.. 200. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production..
201. Feb 18 Brian Handy Re: New 3.0 SNAPshot CDROM about ready for production.. 202. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production.. 203. Feb 18 John Kelly Re: New 3.0 SNAPshot CDROM about ready for production.. 204. Feb 18 Jordan K. Hubbard Re: New 3.0 SNAPshot CDROM about ready for production.. 205. Feb 18 John Kelly Re: New 3.0 SNAPshot CDROM about ready for production.. 206. Feb 18 Amancio Hasty Re: New 3.0 SNAPshot CDROM about ready for production.. 207. Feb 18 John Polstra Re: New 3.0 SNAPshot CDROM about ready for production.. 208. Feb 18 Amancio Hasty Re: New 3.0 SNAPshot CDROM about ready for production.. 209. Feb 19 Snob Art Genre Re: New 3.0 SNAPshot CDROM about ready for production.. 210. Feb 20 Julian Elischer New SoftUpdates test kit 211. Feb 20 Chris Csanady Re: New SoftUpdates test kit 212. Feb 20 Matthew N. Dodd Re: New SoftUpdates test kit 213. Feb 21 Julian Elischer Re: New SoftUpdates test kit 214. Feb 21 Julian Elischer Re: New SoftUpdates test kit 215. Feb 21 Greg Lehey Re: New SoftUpdates test kit 216. Feb 21 Mike Smith Re: New SoftUpdates test kit 217. Feb 21 Greg Lehey Re: New SoftUpdates test kit 218. Feb 21 Mike Smith Re: New SoftUpdates test kit 219. Feb 15 Mark Mayo Re: NFS CLIENT/SERVER LOCKING PATCHES NOW WORKING 220. Feb 15 Kevin Day panic: rslock
221. Feb 16 Terry Lambert Re: panic: rslock 222. Feb 16 Kevin Day Re: panic: rslock 223. Feb 17 Wolfgang Helbig Re: panic: rslock 224. Feb 17 Wolfgang Helbig Re: panic: rslock 225. Feb 21 Kevin Day panic: rslock: cpu: 1 during boot on current kernel (was: panic: vm_page_unwire: i 226. Feb 21 John S. Dyson Re: panic: rslock: cpu: 1 during boot on current kernel (was: panic: vm_page_unwir 227. Feb 18 Alejandro Mery Pellegrini panic: vm_page_free 228. Feb 18 Jordan K. Hubbard Re: panic: vm_page_free 229. Feb 20 Kevin Day panic: vm_page_unwire: invalid wire count: 0 230. Feb 21 Kevin Day Re: panic: vm_page_unwire: invalid wire count: 0 231. Feb 21 Kevin Day Re: panic: vm_page_unwire: invalid wire count: 0 232. Feb 21 Andrew Gallatin Re: panic: vm_page_unwire: invalid wire count: 0 233. Feb 18 Axel Thimm panic: vm_page_unwire: invalid wire count: 0 (was Re: getcwd, fork & vfork) 234. Feb 18 Jordan K. Hubbard Re: panic: vm_page_unwire: invalid wire count: 0 (was Re: getcwd, fork & vfork 235. Feb 18 Luigi Rizzo ppp and RED 236. Feb 18 Luigi Rizzo Re: ppp and RED 237. Feb 18 Kenjiro Cho Re: ppp and RED 238. Feb 15 Superuser Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT 239. Feb 15 Mike Smith Re: Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT 240. Feb 15 John S. Dyson Re: Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT
241. Feb 16 Satoshi Asami Re: Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT 242. Feb 16 Superuser Re: Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT 243. Feb 19 V Edward Gold, Jr. problems with XView and FreeBSD 244. Feb 16 Amancio Hasty soft update, panic... 245. Feb 16 David Greenman Re: soft update, panic... 246. Feb 16 Poul-Henning Kamp Re: soft update, panic... 247. Feb 15 Amancio Hasty soft updates , panic 248. Feb 15 Terry Lambert Soft updates: OPTIONS Vs. TUNABLES, and a plan... 249. Feb 16 Terry Lambert Re: Soft updates: OPTIONS Vs. TUNABLES, and a plan... 250. Feb 20 Edwin Culp SoftUpdates test kit 251. Feb 21 Julian Elischer Re: SoftUpdates test kit 252. Feb 16 brian@worldcontrol.com softupdates4 + kirk.tar.gz 4 buildworld success 253. Feb 16 Amancio Hasty Re: softupdates4 + kirk.tar.gz 4 buildworld success 254. Feb 17 brian@worldcontrol.com softupdates4 ruins performance of my wide drive 8-) 255. Feb 17 Satoshi Asami Re: softupdates4 ruins performance of my wide drive 8-) 256. Feb 17 Terry Lambert Re: softupdates4 ruins performance of my wide drive 8-) 257. Feb 20 Alfred Perlstein SVGAlib 258. Feb 20 Mike Smith Re: SVGAlib 259. Feb 16 Alex Le Heux swap broken too 260. Feb 16 John S. Dyson Re: swap broken too
261. Feb 21 Chris Csanady swap_pager: suggest more swap space: 125 MB ?!! 262. Feb 16 Andrew N. Edmond (Nero) The Adaptec 7895 (again)... 263. Feb 20 John Birrell timecounter stuff in sys/time.h 264. Feb 21 =?koi8-r?B?4c7E0sXKIP7F0s7 Unknown kernel config option, please add 265. Feb 21 Eivind Eklund Re: Unknown kernel config option, please add 266. Feb 21 dave adkins v1.111 of clock.c missing CLOCK_UNLOCK in i8254_get_timecount() 267. Feb 21 Jordan K. Hubbard Re: v1.111 of clock.c missing CLOCK_UNLOCK in i8254_get_timecount() 268. Feb 17 Alejandro Mery Pellegrini vfat & fat32 patch 269. Feb 17 Doug White Re: vfat & fat32 patch 270. Feb 19 Johan Larsson Re: vfat & fat32 patch 271. Feb 15 freebsd@isvara.net Re: VM messed: vm_page_free panic problem 272. Feb 18 Alex Le Heux weird things happening 273. Feb 18 Alfred Perlstein Re: weird things happening 274. Feb 21 Alfred Perlstein weirdness in the header files. 275. Feb 16 Alex Povolotsky What snap to build? 276. Feb 16 sthaug@nethelp.no Re: What snap to build? 277. Feb 18 osa@unibest.ru Where is opt_*.h ??? 278. Feb 19 Eivind Eklund Re: Where is opt_*.h ??? 279. Feb 19 freebsd@isvara.net Re: Where is opt_*.h ??? 280. Feb 15 brian@worldcontrol.com Re: Working (apparently) soft-update code available.
281. Feb 15 Alex Re: Working (apparently) soft-update code available. 282. Feb 15 Open Systems Networking Re: Working (apparently) soft-update code available. 283. Feb 15 Philippe Regnauld Re: Working (apparently) soft-update code available. 284. Feb 15 Amancio Hasty Re: Working (apparently) soft-update code available. 285. Feb 15 brian@worldcontrol.com Re: Working (apparently) soft-update code available. 286. Feb 15 brian@worldcontrol.com Re: Working (apparently) soft-update code available. 287. Feb 15 Ollivier Robert Re: Working (apparently) soft-update code available. 288. Feb 15 Amancio Hasty Re: Working (apparently) soft-update code available. 289. Feb 15 brian@worldcontrol.com Re: Working (apparently) soft-update code available. 290. Feb 15 Amancio Hasty Re: Working (apparently) soft-update code available. 291. Feb 16 Julian Elischer Re: Working (apparently) soft-update code available. 292. Feb 16 Julian Elischer Re: Working (apparently) soft-update code available. 293. Feb 16 Amancio Hasty Re: Working (apparently) soft-update code available. 294. Feb 16 Julian Elischer Re: Working (apparently) soft-update code available.
home | up | archive sorted by: subject | author | date | reverse date