o Add bsdtalk 111,110,109
o Add NYCBUG pkgsrcCon talk
o Add OpenBSD Release Songs
o Add "Linux and FreeBSD video tutorials. For everyone." and initial catchup.
PR: docs/112693
Submitted by: edwin
Quoting submitter:
Even though the list is for *BSD and not only FreeBSD, FreeBSD
is the most used OS on the list, and I feel this is the most
appropriate place to ask questions about FreeBSD in Norwegian.
Submitted by: anders
1. Remove the "Download instructions"
- The mentioned site is not updated any longer so it's just
confusing for newbies.
- Most newbies don't download via FTP. Even if they
do, they will normally download the ISO-images, not the
different distributions.
- www/en/where.sgml already describes how to get FreeBSD
and is up-to-date.
2. "The Complete FreeBSD"
- This book can be downloaded free of charge since 2006 from
http://www.lemis.com/grog/Documentation/CFBSD/. So link to
this site.
3. article "new-users".
- It has been in the doc-tree for a long time now. So link
to it.
- The docs at the also mentioned FTP-site are outdated.
Recent versions are available from the FreeBSD.org servers
(just like the article itself).
Discussed with/approved by: remko@ (mentor)
Content-Disposition header.
- When downloading/referring to a particular patch embed the patch
number with the PR instead of using two different CGI variables.
This means that there aren't "&" in the patch URL's anymore which
makes things simpler for sh(1) like shells, by not requiring quoting
of URLs when using a command line tool, such as fetch(1), to
download patches.
- In HTML-ifying of URL's, handle when a URL contains a PR like string
which can e.g. be seen in PR www/113071.
- Add a comment about how to test script via the command line.
Submitted by: edwin, shaun
PR: www/113071
where no page was returned to the submitter resulting in many
duplicate PR's.
The pipe to sendmail was just being closed without the nice ".\n" to
tell sendmail this is the end of the mail. Now we always send "\n.\n"
to be sure the is a standalone "." on a line.
Why this wasn't a problem before, but is now, I'm not really sure, but
it's probably a perl 5.0 -> 5.8 change which triggered this.
If there are still problems after this commit, please report including
PR number(s).
Prodded by: bugmeister(s)
Co-prodding and testing help: edwin
Not fixed for far too long by: simon
