|
Revision tags: release/14.0.0 |
|
| #
d0b2dbfa |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
| #
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
show more ...
|
|
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 |
|
| #
c165f4ab |
| 18-Mar-2020 |
Hiroki Sato <hrs@FreeBSD.org> |
-F is GNU diff specific, not implemented in BSD diff.
Reported by: kouya@ryuhoku.jp
MFC after: 3 days
|
|
Revision tags: release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
| #
f0cfa1b1 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
share and pc-sysinstall: 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
share and pc-sysinstall: 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.
Commit these apart because compile testing doesn't guarantee I didn't made
some nasty mistake. 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, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, 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, release/4.10.0_cvs, release/4.10.0, 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 |
|
| #
978243bd |
| 07-Sep-2003 |
John-Mark Gurney <jmg@FreeBSD.org> |
make sure we really don't have a tty when installing rules. This prevents
a flush command from asking a question (you can't see):
If there is no tty associated with the process, this is implied.
MF
make sure we really don't have a tty when installing rules. This prevents
a flush command from asking a question (you can't see):
If there is no tty associated with the process, this is implied.
MFC after: 1 day
show more ...
|
|
Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0 |
|
| #
f212b184 |
| 13-Feb-2003 |
Christian Brueffer <brueffer@FreeBSD.org> |
Various spelling and grammar fixes
PR: 44312
Submitted by: Chris Pepper <pepper@rockefeller.edu>
MFC after: 3 days
|
|
Revision tags: release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs |
|
| #
256ab0ef |
| 30-Sep-2001 |
Sheldon Hearn <sheldonh@FreeBSD.org> |
1) Fix change_rules.sh for the case where firewall_type provides the
name of a file containing ipfw rules.
2) Replace the use of a predictable temporary filename with one
generated by mktemp(1
1) Fix change_rules.sh for the case where firewall_type provides the
name of a file containing ipfw rules.
2) Replace the use of a predictable temporary filename with one
generated by mktemp(1).
3) Only exit with a zero exit status if the rules were updated.
4) Use a pager to view the new rules, not an editor.
I was told by dcs that this script's original author is no longer
interested in FreeBSD and would not wish to review this patch.
show more ...
|
| #
29d19e86 |
| 18-Jun-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Make this really work.
|
| #
db97c662 |
| 06-Jun-2001 |
Daniel C. Sobral <dcs@FreeBSD.org> |
Use ${EDITOR} as claimed.
Source rc.conf and use ${firewall_script} instead of rc.firewall.
Textwidth formatting of comments and text.
PR:
Submitted by: Maxim <maxim@news1.macomnet.ru>
(sorry if
Use ${EDITOR} as claimed.
Source rc.conf and use ${firewall_script} instead of rc.firewall.
Textwidth formatting of comments and text.
PR:
Submitted by: Maxim <maxim@news1.macomnet.ru>
(sorry if I got name/email/committer status wrong :)
show more ...
|
| #
7b4d3c72 |
| 06-Jun-2001 |
Daniel C. Sobral <dcs@FreeBSD.org> |
Introduce an example script of safe changing of ipfw(8) rules.
I'm sure this can be much improved, but this works fairly well.
PR: 27887
Submitted by: Alexandre Peixoto <alexandref@tcoip.com.br>
M
Introduce an example script of safe changing of ipfw(8) rules.
I'm sure this can be much improved, but this works fairly well.
PR: 27887
Submitted by: Alexandre Peixoto <alexandref@tcoip.com.br>
MFC after: 1 week
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, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, 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, release/4.10.0_cvs, release/4.10.0, 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 |
|
| #
978243bd |
| 07-Sep-2003 |
John-Mark Gurney <jmg@FreeBSD.org> |
make sure we really don't have a tty when installing rules. This prevents
a flush command from asking a question (you can't see):
If there is no tty associated with the process, this is implied.
MF
make sure we really don't have a tty when installing rules. This prevents
a flush command from asking a question (you can't see):
If there is no tty associated with the process, this is implied.
MFC after: 1 day
show more ...
|
|
Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0 |
|
| #
f212b184 |
| 13-Feb-2003 |
Christian Brueffer <brueffer@FreeBSD.org> |
Various spelling and grammar fixes
PR: 44312
Submitted by: Chris Pepper <pepper@rockefeller.edu>
MFC after: 3 days
|
|
Revision tags: release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs, release/4.5.0_cvs, release/4.4.0_cvs |
|
| #
256ab0ef |
| 30-Sep-2001 |
Sheldon Hearn <sheldonh@FreeBSD.org> |
1) Fix change_rules.sh for the case where firewall_type provides the
name of a file containing ipfw rules.
2) Replace the use of a predictable temporary filename with one
generated by mktemp(1
1) Fix change_rules.sh for the case where firewall_type provides the
name of a file containing ipfw rules.
2) Replace the use of a predictable temporary filename with one
generated by mktemp(1).
3) Only exit with a zero exit status if the rules were updated.
4) Use a pager to view the new rules, not an editor.
I was told by dcs that this script's original author is no longer
interested in FreeBSD and would not wish to review this patch.
show more ...
|
| #
29d19e86 |
| 18-Jun-2001 |
Ruslan Ermilov <ru@FreeBSD.org> |
Make this really work.
|
| #
db97c662 |
| 06-Jun-2001 |
Daniel C. Sobral <dcs@FreeBSD.org> |
Use ${EDITOR} as claimed.
Source rc.conf and use ${firewall_script} instead of rc.firewall.
Textwidth formatting of comments and text.
PR:
Submitted by: Maxim <maxim@news1.macomnet.ru>
(sorry if
Use ${EDITOR} as claimed.
Source rc.conf and use ${firewall_script} instead of rc.firewall.
Textwidth formatting of comments and text.
PR:
Submitted by: Maxim <maxim@news1.macomnet.ru>
(sorry if I got name/email/committer status wrong :)
show more ...
|
| #
7b4d3c72 |
| 06-Jun-2001 |
Daniel C. Sobral <dcs@FreeBSD.org> |
Introduce an example script of safe changing of ipfw(8) rules.
I'm sure this can be much improved, but this works fairly well.
PR: 27887
Submitted by: Alexandre Peixoto <alexandref@tcoip.com.br>
M
Introduce an example script of safe changing of ipfw(8) rules.
I'm sure this can be much improved, but this works fairly well.
PR: 27887
Submitted by: Alexandre Peixoto <alexandref@tcoip.com.br>
MFC after: 1 week
show more ...
|