History log of /freebsd-10.0-release/usr.bin/printenv/
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
259065 07-Dec-2013 gjb

- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation


216370 11-Dec-2010 joel

Remove the advertising clause from UCB copyrighted files in usr.bin. This
is in accordance with the information provided at
ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change

Also add $FreeBSD$ to a few files to keep svn happy.

Discussed with: imp, rwatson


188889 21-Feb-2009 delphij

Define extern **environ in global scope instead of in function.


165553 26-Dec-2006 ru

Simplify.


140368 17-Jan-2005 ru

Added the EXIT STATUS section where appropriate.


115603 01-Jun-2003 tjr

Split the env(1) manpage off from printenv(1); there is not much point
in keeping them together. Mention that printenv is obsolescent.


107276 26-Nov-2002 ru

mdoc(7) police: markup polishing.

Approved by: re


102944 04-Sep-2002 dwmalone

ANSIify function definitions.
Add some constness to avoid some warnings.
Remove use register keyword.
Deal with missing/unneeded extern/prototypes.
Some minor type changes/casts to avoid warnings.

Reviewed by: md5


98969 28-Jun-2002 tjr

Document the fairly obvious effects of the PATH environment variable.


98968 28-Jun-2002 tjr

Discourage use of env(1)'s "-" flag by moving its description to the
Compatibility section of the manual page.


98418 19-Jun-2002 tjr

Indicate that env(1) allows you to supply arguments to the utility it
executes in the usage() message and manual page. Use "utility" instead of
"command" in both places to emphasise that shell builtins etc. will not work,
and to be consistent with the terminology used by POSIX.

PR: 39210
Submitted by: Danny J. Zerkel <dzerkel@columbus.rr.com>
MFC after: 1 week


95124 20-Apr-2002 charnier

Use `The .Nm utility'


92921 22-Mar-2002 imp

remove __P


91004 21-Feb-2002 mike

Use new ID scheme.

Fix env(1)'s exit status to conform with SUSv3.

Submitted by: Tim Robbins <tim@robbins.dropbear.id.au>
MFC after: 2 weeks


90415 08-Feb-2002 markm

Remove leaf node WARNS?=2 (that mainly I added). This should
help the GCC3 transition and CURRENT in general.


87628 10-Dec-2001 dwmalone

Style improvements recommended by Bruce as a follow up to some
of the recent WARNS commits. The idea is:

1) FreeBSD id tags should follow vendor tags.
2) Vendor tags should not be compiled (though copyrights probably should).
3) There should be no blank line between including cdefs and __FBSDIF.


87294 03-Dec-2001 dwmalone

Warnc cleanups. Add FreeBSD IDs.


79278 05-Jul-2001 ru

mdoc(7) police: fixed formatting.


77453 30-May-2001 dd

Mention how env(1) can be used with the "#!" construct.

PR: 27690
Submitted by: Mike Meyer <mwm@mired.org>


70197 19-Dec-2000 ru

Prepare for mdoc(7)NG.


68963 20-Nov-2000 ru

mdoc(7) police: use the new features of the Nm macro.


60262 09-May-2000 sheldonh

The printenv(1) command is now a builtin(1) in csh(1).


57670 01-Mar-2000 sheldonh

Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.


50477 28-Aug-1999 peter

$Id$ -> $FreeBSD$


50444 27-Aug-1999 sheldonh

Add ``-i'' option, which is the same as ``-''. The -i option is the
recommended option in the manpage, but the - option remains for
backward compatibility and is documented as such.

PR: 13363
Reported by: James Howard <howardjp@wam.umd.edu>
Reviewed by: bde


48792 12-Jul-1999 nik

Add $Id$, to make it simpler for members of the translation teams to
track.

The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;

.\" $Id$
.\"

If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.

Approved by: bde


27886 04-Aug-1997 charnier

environmental -> environment.


24360 29-Mar-1997 imp

compare return value from getopt against -1 rather than EOF, per the final
posix standard on the topic.


23691 11-Mar-1997 peter

This commit was generated by cvs2svn to compensate for changes in r23690,
which included commits to RCS files with non-trunk default branches.


1591 27-May-1994 rgrimes

This commit was generated by cvs2svn to compensate for changes in r1590,
which included commits to RCS files with non-trunk default branches.