#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] 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
|
#
251069 |
|
28-May-2013 |
emaste |
Renumber clauses to reduce diffs to other versions
NetBSD, OpenBSD, and Android's Bionic number the clauses 1 through 3, so follow suit to make comparison easier.
|
#
235286 |
|
11-May-2012 |
gjb |
General mdoc(7) and typo fixes.
PR: 167734 Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org) MFC after: 3 days
|
#
233648 |
|
29-Mar-2012 |
eadler |
Remove trailing whitespace per mdoc lint warning
Disussed with: gavin No objection from: doc Approved by: joel MFC after: 3 days
|
#
200195 |
|
07-Dec-2009 |
scf |
Update the getenv(3) man page to reflect the recent change to the behavior of setenv(), putenv() and unsetenv() when dealing with corrupt entries in environ. They now output a warning and complete their task without error.
MFC after: 1 week
|
#
171195 |
|
04-Jul-2007 |
scf |
Significantly reduce the memory leak as noted in BUGS section for setenv(3) by tracking the size of the memory allocated instead of using strlen() on the current value.
Convert all calls to POSIX from historic BSD API: - unsetenv returns an int. - putenv takes a char * instead of const char *. - putenv no longer makes a copy of the input string. - errno is set appropriately for POSIX. Exceptions involve bad environ variable and internal initialization code. These both set errno to EFAULT.
Several patches to base utilities to handle the POSIX changes from Andrey Chernov's previous commit. A few I re-wrote to use setenv() instead of putenv().
New regression module for tools/regression/environ to test these functions. It also can be used to test the performance.
Bump __FreeBSD_version to 700050 due to API change.
PR: kern/99826 Approved by: wes Approved by: re (kensmith)
|
#
169177 |
|
01-May-2007 |
ache |
Back out all POSIXified *env() changes.
Not because I admit they are technically wrong and not because of bug reports (I receive nothing). But because I surprisingly meets so strong opposition and resistance so lost any desire to continue that.
Anyone who interested in POSIX can dig out what changes and how through cvs diffs.
|
#
169146 |
|
30-Apr-2007 |
ache |
Bump .Dd
Suggested by: Henrik Brix Andersen <henrik@brixandersen.dk>
|
#
169142 |
|
30-Apr-2007 |
ache |
Add phrase "so altering the argument shall change the environment." into putenv description.
|
#
169138 |
|
30-Apr-2007 |
ache |
Make putenv() fully conforms to Open Group specs Issue 6 (also IEEE Std 1003.1-2001)
The specs explicitly says that altering passed string should change the environment, i.e. putenv() directly puts its arg into environment (unlike setenv() which just copies it there). It means that putenv() can't be implemented via setenv() (like we have before) at all. Putenv() value lives (allows modifying) up to the next putenv() or setenv() call.
|
#
169111 |
|
30-Apr-2007 |
ache |
Remove special case skipping initial '=' of the setenv() value "for compatibility with the different environment conventions" (man page). With the standards, we don't have them different anymore and IEEE Std 1003.1-2001 says that
"The values that the environment variables may be assigned are not restricted except that they are considered to end with a null byte"
|
#
169109 |
|
30-Apr-2007 |
ache |
Make setenv, putenv, getenv and unsetenv conforming to Open Group specs Issue 6 (also IEEE Std 1003.1-2001) in following areas: args, return, errors.
Putenv still needs rewriting because specs explicitly says that altering passed string later should change the environment (currently we copy the string so can't provide that).
|
#
165903 |
|
09-Jan-2007 |
imp |
Per Regents of the University of Calfornia letter, remove advertising clause.
# If I've done so improperly on a file, please let me know.
|
#
163262 |
|
12-Oct-2006 |
trhodes |
Note that the value from getenv() should not be modified by applications.
PR: 60544 Reviewed by: ru
|
#
163108 |
|
07-Oct-2006 |
trhodes |
getenv.3: Put "is" on a line with other words getobjformat.3: "takes precedence over" is not an envrionment variable.
PR: 75545 Submitted by: n-kogane@syd.odn.ne.jp MFC after: 3 days
|
#
140505 |
|
20-Jan-2005 |
ru |
Sort sections.
|
#
131754 |
|
07-Jul-2004 |
ru |
mdoc(7) fixes.
|
#
131728 |
|
06-Jul-2004 |
hmp |
Move the return value information about the getenv(3) library function under the RETURN VALUES section so it is consistent with others.
Cleanup the return value text for getenv(3) a little while I am here.
PR: docs/58033 MFC after: 3 days
|
#
131504 |
|
02-Jul-2004 |
ru |
Mechanically kill hard sentence breaks.
|
#
108040 |
|
18-Dec-2002 |
ru |
mdoc(7) police: Fixed abuses of the .Ar and .Em macros.
|
#
83206 |
|
07-Sep-2001 |
asmodai |
Move to using .In instead of .Fd #include <> for include mark-up.
Inspired by comment from: dd
|
#
82642 |
|
31-Aug-2001 |
ru |
Use ``.Rv -std'' wherever possible.
Submitted by: yar
|
#
79754 |
|
15-Jul-2001 |
dd |
Remove whitespace at EOL.
|
#
73088 |
|
26-Feb-2001 |
ru |
.St -ansiC -> .St -isoC
|
#
71895 |
|
01-Feb-2001 |
ru |
mdoc(7) police: split punctuation characters + misc fixes.
|
#
68716 |
|
14-Nov-2000 |
ru |
Use Fx macro wherever possible.
|
#
60075 |
|
06-May-2000 |
phantom |
Use `Er' variable to define first column width in ERRORS section.
|
#
59460 |
|
21-Apr-2000 |
phantom |
Introduce ".Lb" macro to libc manpages.
More libraries manpages updates following.
|
#
56652 |
|
26-Jan-2000 |
archie |
Document the memory leak that is inherent in FreeBSD's semantics for getenv()/putenv().
PR: 10341 5604
|
#
50476 |
|
28-Aug-1999 |
peter |
$Id$ -> $FreeBSD$
|
#
48794 |
|
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
|
#
1574 |
|
27-May-1994 |
rgrimes |
This commit was generated by cvs2svn to compensate for changes in r1573, which included commits to RCS files with non-trunk default branches.
|
#
1573 |
|
27-May-1994 |
rgrimes |
BSD 4.4 Lite Lib Sources
|