"f6234b51" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:f6234b51 (Results 1 – 8 of 8) sorted by relevance

/freebsd/usr.bin/top/
H A D	username.h	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense
H A D	username.c	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense
H A D	screen.c	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense
H A D	machine.h	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense
H A D	commands.c	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense
H A D	utils.c	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense
H A D	display.c	`f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense`
H A D	top.c	f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense f6234b51 Sat Jun 02 00:02:15 GMT 2018 Eitan Adler <eadler@FreeBSD.org> top(1): ansify, style(9). and nits - Prefer using ansi prototypes rather than C prototypes - Keep type on separate line from name of function - Try to keep things const where possible. This will help get to WARNS=6 - switch to "bool" where it makes sense