#
302408 |
|
07-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
300683 |
|
25-May-2016 |
pfg |
libc: regexec(3) adjustment.
Change the behavior of when REG_STARTEND is combined with REG_NOTBOL.
From the original posting[1]:
"Enable the assumption that pmatch[0].rm_so is a continuation offset to a string and allows us to do a proper assessment of the character in regards to it's word position ('^' or '\<'), without risking going into unallocated memory."
This change makes us similar to how glibc handles REG_STARTEND | REG_NOTBOL, and is closely related to a soon-to-land fix to sed.
Special thanks to Martijn van Duren and Ingo Schwarze for working out some consistent behaviour.
Differential Revision: https://reviews.freebsd.org/D6257 Taken from: openbsd-tech 2016-05-24 [1] (Martijn van Duren) Relnotes: yes MFC after: 1 month
|
#
282007 |
|
26-Apr-2015 |
bapt |
mdoc: rendering fixes
|
#
165903 |
|
08-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.
|
#
149179 |
|
17-Aug-2005 |
tjr |
Document the fact that word-boundary matching does not work properly in multibyte locales.
|
#
141846 |
|
13-Feb-2005 |
ru |
Expand *n't contractions.
|
#
140505 |
|
20-Jan-2005 |
ru |
Sort sections.
|
#
132031 |
|
12-Jul-2004 |
tjr |
Remove an entry from the BUGS section: we have multibyte character support now.
|
#
132017 |
|
12-Jul-2004 |
tjr |
Add a new error code, REG_ILLSEQ, to indicate that a regular expression contains an illegal multibyte character sequence.
|
#
131692 |
|
06-Jul-2004 |
tjr |
Document incorrect handling of multibyte characters.
|
#
131504 |
|
02-Jul-2004 |
ru |
Mechanically kill hard sentence breaks.
|
#
119893 |
|
08-Sep-2003 |
ru |
mdoc(7): Use the new feature of the .In macro.
|
#
108087 |
|
19-Dec-2002 |
ru |
mdoc(7) police: "The .Fa argument.".
|
#
108037 |
|
18-Dec-2002 |
ru |
mdoc(7) police: "The .Fn function".
|
#
104358 |
|
02-Oct-2002 |
mike |
Add restrict type-qualifier.
|
#
84306 |
|
01-Oct-2001 |
ru |
mdoc(7) police: Use the new .In macro for #include statements.
|
#
81449 |
|
10-Aug-2001 |
ru |
mdoc(7) police: protect trailing full stops of abbreviations with a trailing zero-width space: `e.g.\&'.
|
#
81251 |
|
07-Aug-2001 |
ru |
mdoc(7) police:
Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text. Not only this slows down the mdoc(7) processing significantly, but it also has an undesired (in this case) effect of disabling hyphenation within the entire enclosed block.
|
#
70966 |
|
12-Jan-2001 |
ru |
man(7) -> mdoc(7).
|
#
62389 |
|
02-Jul-2000 |
dcs |
Remove from the notes a bug that it's said to have been fixed.
PR: 15561 Submitted by: Martin Kammerhofer <mkamm@gmx.net> Confirmed by: ache
|
#
50476 |
|
27-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
|
#
17782 |
|
22-Aug-1996 |
mpp |
Correctly use .Fn instead of .Nm to reference function names in a bunch of man pages.
Use the correct .Bx (BSD UNIX) or .At (AT&T UNIX) macros instead of explicitly specifying the version in the text in a bunch of man pages.
|
#
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
|