wiz 584772619f Document that patch file names should contain the path and file name. ... E.g. for lib/bar/foo_bar.c the patch file name should be patch-lib_bar_foo__bar.c The previous convention is still mentioned. While here, give more good hints about how to handle patches: * always add comments * when sent upstream, note bug reporting URL		2011-02-02 10:25:36 +00:00
..
share
binary.xml
build.xml	Add a note about URLs starting with a dash.	2009-08-02 02:41:53 +00:00
buildlink.xml
bulk.xml	Update documentation since vulnerable packages are not moved	2010-03-18 10:56:18 +00:00
chapters.ent
components.xml	Document that patch file names should contain the path and file name.	2011-02-02 10:25:36 +00:00
configuring.xml	remove outdated references to USE_CPUFLAGS	2010-12-23 23:54:17 +00:00
creating.xml	Retire Python 2.3 support.	2009-09-07 18:22:10 +00:00
debug.xml
devfaq.xml
editing.xml
examples.xml
faq.xml	remove outdated references to USE_CPUFLAGS	2010-12-23 23:54:17 +00:00
files.xml
fixes.xml	Document PKG_JAVA_HOME, from Francois Tigeot.	2011-01-16 08:40:28 +00:00
ftp-layout.xml	We are heading towards 2010, which makes year references like	2009-10-11 20:50:48 +00:00
getting.xml	Simplify CVS instructions:	2010-12-23 10:42:16 +00:00
gnome.xml
infr.design.xml
introduction.xml	Note Haiku OS.	2010-09-30 12:21:51 +00:00
logs.xml
Makefile
makefile.xml
options.xml
pkginstall.xml
pkgsrc.ent
pkgsrc.xml
platforms.xml	Mention that Interix 6.1 (64bit) is tested (reported by J in private email).	2011-01-03 20:14:27 +00:00
plist.xml	Close tag.	2009-08-25 13:19:50 +00:00
porting.xml
regression.xml
submit.xml	fix capitalization of NetBSD.org	2009-09-17 18:01:18 +00:00
tools.xml
using.xml	Update documentation since vulnerable packages are not moved	2010-03-18 10:56:18 +00:00