You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the source trees of *BSD projects, some binary files are sometimes present (e.g. font, firmware and architecture-specific files), and are often encoded with uuencode.
As it stands, this results in a lot of rubbish being indexed, and those files, once converted to xref/, contain a lot of links for random paths, as / is one of the characters of the uuencode encoding.
In the source trees of *BSD projects, some binary files are sometimes present (e.g. font, firmware and architecture-specific files), and are often encoded with
uuencode
.As it stands, this results in a lot of rubbish being indexed, and those files, once converted to
xref/
, contain a lot of links for random paths, as/
is one of the characters of theuuencode
encoding.http://bxr.su/search?q=begin&path=fnt+OR+uu+OR+uue
For bxr.su, I wrote a simple parser, that only indexes the top and the bottom portions of such files, skipping all the
uuencode
content.The text was updated successfully, but these errors were encountered: