Revision tags: release/14.0.0 |
|
#
b3e76948 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
#
1de7b4b8 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0 |
|
#
93b9f504 |
| 16-Jan-2008 |
Xin LI <delphij@FreeBSD.org> |
ANSIfy and remove register.
Resulting binary verified with strip(1)+md5(1).
|
Revision tags: release/6.3.0_cvs, release/6.3.0 |
|
#
bc68fcf3 |
| 18-Jan-2007 |
Ruslan Ermilov <ru@FreeBSD.org> |
Fix definitions of kilobits etc.
PR: bin/106116 Nudged by: Rostislav Krasny MFC after: 3 days
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
dfaa9125 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Add the Tera scale factor, which is an easy job now. More scale factors would overflow the command line where the help for "scale" were shown.
|
#
afe7b9fb |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Stop exposing things that can be private to convtbl.c.
|
#
aee371e3 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Keep all convtbl-related constants and strings in convtbl.[ch].
|
#
f5d4751c |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Allow for large scale factors. C99 warrants that ULLONG_MAX is not less than 2^64-1; and uintmax_t cannot be more narrow than unsigned long long. This allows for scale factors up to Exa inclusively.
Allow for large scale factors. C99 warrants that ULLONG_MAX is not less than 2^64-1; and uintmax_t cannot be more narrow than unsigned long long. This allows for scale factors up to Exa inclusively.
Use plain int for the scale index to be consistent with ifcmds.c and enum.
show more ...
|
#
f3014885 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
+ Drop useless initializers. + style(9).
|
#
02303837 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Use C99 initializers so that we don't really have to worry about the order of related things at several places.
|
#
00603ea2 |
| 26-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
There is no reason to use __inline here because we are rather far from a path critical to performance.
|
#
a3736d31 |
| 26-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Don't overflow from the gigabyte scale to the bit scale if the number to auto-scale is >= 1024 Gb. Could be triggered on arches where ifdata counters had 64 bits.
Reported by: Miroslav Slavkov on -
Don't overflow from the gigabyte scale to the bit scale if the number to auto-scale is >= 1024 Gb. Could be triggered on arches where ifdata counters had 64 bits.
Reported by: Miroslav Slavkov on -net MFC after: 3 days
show more ...
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0 |
|
#
5908d366 |
| 04-Jul-2004 |
Stefan Farfeleder <stefanf@FreeBSD.org> |
Consistently use __inline instead of __inline__ as the former is an empty macro in <sys/cdefs.h> for compilers without support for inline.
|
Revision tags: release/4.10.0_cvs, release/4.10.0 |
|
#
33dc5491 |
| 09-Mar-2004 |
David Malone <dwmalone@FreeBSD.org> |
Fix the easy warnings:
1) Avoid shadowing index. 2) Constness. 3) Missing prototype for ifcmd. 4) Missing include of string.h. 5) Avoid shadowing error function. 6) ANSI definition for main.
|
Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0 |
|
#
b59ba7df |
| 04-Jan-2003 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Add "ifstat" display:
ifstat Display the network traffic going through active interfaces on the system. Idle interfaces will not be displayed until they
Add "ifstat" display:
ifstat Display the network traffic going through active interfaces on the system. Idle interfaces will not be displayed until they receive some traffic.
For each interface being displayed, the current, peak and total statistics are displayed for incoming and outgoing traffic. By default, the ifstat display will automatically scale the units being used so that they are in a human-read- able format. The scaling units used for the current and peak traffic columns can be altered by the scale command.
Submitted by: Trent Nelson <trent@arpa.com>
show more ...
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0, release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0 |
|
#
93b9f504 |
| 16-Jan-2008 |
Xin LI <delphij@FreeBSD.org> |
ANSIfy and remove register.
Resulting binary verified with strip(1)+md5(1).
|
Revision tags: release/6.3.0_cvs, release/6.3.0 |
|
#
bc68fcf3 |
| 18-Jan-2007 |
Ruslan Ermilov <ru@FreeBSD.org> |
Fix definitions of kilobits etc.
PR: bin/106116 Nudged by: Rostislav Krasny MFC after: 3 days
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
dfaa9125 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Add the Tera scale factor, which is an easy job now. More scale factors would overflow the command line where the help for "scale" were shown.
|
#
afe7b9fb |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Stop exposing things that can be private to convtbl.c.
|
#
aee371e3 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Keep all convtbl-related constants and strings in convtbl.[ch].
|
#
f5d4751c |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Allow for large scale factors. C99 warrants that ULLONG_MAX is not less than 2^64-1; and uintmax_t cannot be more narrow than unsigned long long. This allows for scale factors up to Exa inclusively.
Allow for large scale factors. C99 warrants that ULLONG_MAX is not less than 2^64-1; and uintmax_t cannot be more narrow than unsigned long long. This allows for scale factors up to Exa inclusively.
Use plain int for the scale index to be consistent with ifcmds.c and enum.
show more ...
|
#
f3014885 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
+ Drop useless initializers. + style(9).
|
#
02303837 |
| 27-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Use C99 initializers so that we don't really have to worry about the order of related things at several places.
|
#
00603ea2 |
| 26-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
There is no reason to use __inline here because we are rather far from a path critical to performance.
|
#
a3736d31 |
| 26-Nov-2006 |
Yaroslav Tykhiy <ytykhiy@gmail.com> |
Don't overflow from the gigabyte scale to the bit scale if the number to auto-scale is >= 1024 Gb. Could be triggered on arches where ifdata counters had 64 bits.
Reported by: Miroslav Slavkov on -
Don't overflow from the gigabyte scale to the bit scale if the number to auto-scale is >= 1024 Gb. Could be triggered on arches where ifdata counters had 64 bits.
Reported by: Miroslav Slavkov on -net MFC after: 3 days
show more ...
|