Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'sed(1)'

This is an experimental report containing PRs for manpage 'sed(1)' as of Fri May 30 07:39:18 2014 UTC. See notes.

PRs for manpage 'sed(1)':
o2014/05/15bin/189827[patch] sed(1) treats some absolute addr2 of `N' command as relative
o2012/10/18bin/172862sed(1) improperly deals with escape chars
o2012/04/11bin/166861bsdgrep(1)/sed(1): bsdgrep -E and sed handle invalid {} constructs strangely
o2012/02/14bin/165120ed(1) and sed(1) - tmp file handling - security and location
o2011/09/15bin/160745sed(1) appends '\n' at the end of binary data (unlike gsed(1))
o2011/07/07bin/158706[regression] sed(1) in 8.2 gives incorrect output compared to 7.4
o2002/07/31bin/41190[patch] sed(1) report the { linenum instead of EOF linenum on pending }
o2002/07/30bin/41159[patch] new sed(1) -c option to allow ; as a separator for b, t and : functions
8 problems total.


GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.