blob: 01cb99ded06f3483a6e5e828dc30c552cd85af4d [file] [log] [blame]
Willy Tarreaub1a34b62010-05-09 22:37:12 +02001 ----------------------
2 HAProxy how-to
3 ----------------------
Willy Tarreaua3ecbd92012-12-28 15:04:05 +01004 version 1.5-dev17
Willy Tarreaub1a34b62010-05-09 22:37:12 +02005 willy tarreau
Willy Tarreaua3ecbd92012-12-28 15:04:05 +01006 2012/12/28
willy tarreau78345332005-12-18 01:33:16 +01007
8
Willy Tarreaub1a34b62010-05-09 22:37:12 +020091) How to build it
10------------------
11
willy tarreau78345332005-12-18 01:33:16 +010012To build haproxy, you will need :
Willy Tarreaub1a34b62010-05-09 22:37:12 +020013 - GNU make. Neither Solaris nor OpenBSD's make work with the GNU Makefile.
Willy Tarreau83b30c12008-05-25 10:32:50 +020014 However, specific Makefiles for BSD and OSX are provided.
Willy Tarreau32e65ef2013-04-02 08:14:29 +020015 - GCC between 2.91 and 4.7. Others may work, but not tested.
willy tarreau78345332005-12-18 01:33:16 +010016 - GNU ld
17
18Also, you might want to build with libpcre support, which will provide a very
Willy Tarreaub1a34b62010-05-09 22:37:12 +020019efficient regex implementation and will also fix some badness on Solaris' one.
willy tarreau78345332005-12-18 01:33:16 +010020
21To build haproxy, you have to choose your target OS amongst the following ones
22and assign it to the TARGET variable :
23
Willy Tarreau83b30c12008-05-25 10:32:50 +020024 - linux22 for Linux 2.2
25 - linux24 for Linux 2.4 and above (default)
26 - linux24e for Linux 2.4 with support for a working epoll (> 0.21)
Willy Tarreau83b30c12008-05-25 10:32:50 +020027 - linux26 for Linux 2.6 and above
Willy Tarreaue0c623d2012-06-04 00:42:09 +020028 - linux2628 for Linux 2.6.28 and above (enables splice and tproxy)
Willy Tarreau83b30c12008-05-25 10:32:50 +020029 - solaris for Solaris 8 or 10 (others untested)
Willy Tarreaub1a34b62010-05-09 22:37:12 +020030 - freebsd for FreeBSD 5 to 8.0 (others untested)
Willy Tarreau8624cab2013-04-02 08:17:43 +020031 - osx for Mac OS/X
Willy Tarreau3b8e9792012-11-22 00:43:09 +010032 - openbsd for OpenBSD 3.1 to 5.2 (others untested)
Willy Tarreau7dec9652012-06-06 16:15:03 +020033 - aix52 for AIX 5.2
Yitzhak Sapir32087312009-06-14 18:27:54 +020034 - cygwin for Cygwin
Willy Tarreau83b30c12008-05-25 10:32:50 +020035 - generic for any other OS.
36 - custom to manually adjust every setting
willy tarreau78345332005-12-18 01:33:16 +010037
38You may also choose your CPU to benefit from some optimizations. This is
39particularly important on UltraSparc machines. For this, you can assign
40one of the following choices to the CPU variable :
41
42 - i686 for intel PentiumPro, Pentium 2 and above, AMD Athlon
43 - i586 for intel Pentium, AMD K6, VIA C3.
44 - ultrasparc : Sun UltraSparc I/II/III/IV processor
Willy Tarreaua5899aa2010-11-28 07:41:00 +010045 - native : use the build machine's specific processor optimizations
willy tarreau78345332005-12-18 01:33:16 +010046 - generic : any other processor or no specific optimization. (default)
47
Willy Tarreau83b30c12008-05-25 10:32:50 +020048Alternatively, you may just set the CPU_CFLAGS value to the optimal GCC options
49for your platform.
50
Willy Tarreauef7341d2009-04-11 19:45:50 +020051You may want to build specific target binaries which do not match your native
52compiler's target. This is particularly true on 64-bit systems when you want
53to build a 32-bit binary. Use the ARCH variable for this purpose. Right now
Willy Tarreaua5899aa2010-11-28 07:41:00 +010054it only knows about a few x86 variants (i386,i486,i586,i686,x86_64), two
55generic ones (32,64) and sets -m32/-m64 as well as -march=<arch> accordingly.
Willy Tarreauef7341d2009-04-11 19:45:50 +020056
willy tarreau78345332005-12-18 01:33:16 +010057If your system supports PCRE (Perl Compatible Regular Expressions), then you
58really should build with libpcre which is between 2 and 10 times faster than
59other libc implementations. Regex are used for header processing (deletion,
60rewriting, allow, deny). The only inconvenient of libpcre is that it is not
61yet widely spread, so if you build for other systems, you might get into
62trouble if they don't have the dynamic library. In this situation, you should
63statically link libpcre into haproxy so that it will not be necessary to
Willy Tarreau83b30c12008-05-25 10:32:50 +020064install it on target systems. Available build options for PCRE are :
willy tarreau78345332005-12-18 01:33:16 +010065
Willy Tarreau83b30c12008-05-25 10:32:50 +020066 - USE_PCRE=1 to use libpcre, in whatever form is available on your system
willy tarreau78345332005-12-18 01:33:16 +010067 (shared or static)
68
Willy Tarreau83b30c12008-05-25 10:32:50 +020069 - USE_STATIC_PCRE=1 to use a static version of libpcre even if the dynamic
70 one is available. This will enhance portability.
71
Willy Tarreau663148c2012-12-12 00:38:22 +010072 - with no option, use your OS libc's standard regex implementation (default).
Willy Tarreau83b30c12008-05-25 10:32:50 +020073 Warning! group references on Solaris seem broken. Use static-pcre whenever
74 possible.
willy tarreau78345332005-12-18 01:33:16 +010075
Willy Tarreau64bc40b2011-03-23 20:00:53 +010076Recent systems can resolve IPv6 host names using getaddrinfo(). This primitive
77is not present in all libcs and does not work in all of them either. Support in
78glibc was broken before 2.3. Some embedded libs may not properly work either,
79thus, support is disabled by default, meaning that some host names which only
80resolve as IPv6 addresses will not resolve and configs might emit an error
81during parsing. If you know that your OS libc has reliable support for
82getaddrinfo(), you can add USE_GETADDRINFO=1 on the make command line to enable
83it. This is the recommended option for most Linux distro packagers since it's
84working fine on all recent mainstream distros. It is automatically enabled on
85Solaris 8 and above, as it's known to work.
86
Willy Tarreaud4508812012-09-10 09:07:41 +020087It is possible to add native support for SSL using the GNU makefile only, and
88by passing "USE_OPENSSL=1" on the make commande line. The libssl and libcrypto
89will automatically be linked with haproxy. Some systems also require libz, so
90if the build fails due to missing symbols such as deflateInit(), then try again
91with "ADDLIB=-lz".
92
William Lallemand82fe75c2012-10-23 10:25:10 +020093It is also possible to include native support for ZLIB to benefit from HTTP
94compression. For this, pass "USE_ZLIB=1" on the "make" command line and ensure
95that zlib is present on the system.
96
willy tarreau78345332005-12-18 01:33:16 +010097By default, the DEBUG variable is set to '-g' to enable debug symbols. It is
98not wise to disable it on uncommon systems, because it's often the only way to
99get a complete core when you need one. Otherwise, you can set DEBUG to '-s' to
100strip the binary.
101
102For example, I use this to build for Solaris 8 :
103
Willy Tarreau83b30c12008-05-25 10:32:50 +0200104 $ make TARGET=solaris CPU=ultrasparc USE_STATIC_PCRE=1
willy tarreau78345332005-12-18 01:33:16 +0100105
Willy Tarreau83b30c12008-05-25 10:32:50 +0200106And I build it this way on OpenBSD or FreeBSD :
willy tarreaud38e72d2006-03-19 20:56:52 +0100107
108 $ make -f Makefile.bsd REGEX=pcre DEBUG= COPTS.generic="-Os -fomit-frame-pointer -mgnu"
109
Willy Tarreau663148c2012-12-12 00:38:22 +0100110And on a classic Linux with SSL and ZLIB support (eg: Red Hat 5.x) :
111
112 $ make TARGET=linux26 CPU=native USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1
113
114And on a recent Linux >= 2.6.28 with SSL and ZLIB support :
Willy Tarreaud4508812012-09-10 09:07:41 +0200115
William Lallemand82fe75c2012-10-23 10:25:10 +0200116 $ make TARGET=linux2628 CPU=native USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1
Willy Tarreaud4508812012-09-10 09:07:41 +0200117
William Lallemand82fe75c2012-10-23 10:25:10 +0200118In order to build a 32-bit binary on an x86_64 Linux system with SSL support
119without support for compression but when OpenSSL requires ZLIB anyway :
Willy Tarreauef7341d2009-04-11 19:45:50 +0200120
Willy Tarreaud4508812012-09-10 09:07:41 +0200121 $ make TARGET=linux26 ARCH=i386 USE_OPENSSL=1 ADDLIB=-lz
Willy Tarreauef7341d2009-04-11 19:45:50 +0200122
Willy Tarreau3b8e9792012-11-22 00:43:09 +0100123The BSD and OSX makefiles do not support build options for OpenSSL nor zlib.
124Also, at least on OpenBSD, pthread_mutexattr_setpshared() does not exist so
125the SSL session cache cannot be shared between multiple processes. If you want
126to enable these options, you need to use GNU make with the default makefile as
127follows :
128
129 $ gmake TARGET=openbsd USE_OPENSSL=1 USE_ZLIB=1 USE_PRIVATE_CACHE=1
130
willy tarreau78345332005-12-18 01:33:16 +0100131If you need to pass other defines, includes, libraries, etc... then please
132check the Makefile to see which ones will be available in your case, and
Willy Tarreau83b30c12008-05-25 10:32:50 +0200133use the USE_* variables in the GNU Makefile, or ADDINC, ADDLIB, and DEFINE
134variables in the BSD makefiles.
willy tarreau78345332005-12-18 01:33:16 +0100135
Willy Tarreau97ec9692010-01-28 20:52:05 +0100136AIX 5.3 is known to work with the generic target. However, for the binary to
137also run on 5.2 or earlier, you need to build with DEFINE="-D_MSGQSUPPORT",
138otherwise __fd_select() will be used while not being present in the libc.
Willy Tarreau7dec9652012-06-06 16:15:03 +0200139If you get build errors because of strange symbols or section mismatches,
140simply remove -g from DEBUG_CFLAGS.
Willy Tarreau97ec9692010-01-28 20:52:05 +0100141
Willy Tarreau32e65ef2013-04-02 08:14:29 +0200142You can easily define your own target with the GNU Makefile. Unknown targets
143are processed with no default option except USE_POLL=default. So you can very
144well use that property to define your own set of options. USE_POLL can even be
145disabled by setting USE_POLL="". For example :
146
147 $ gmake TARGET=tiny USE_POLL="" TARGET_CFLAGS=-fomit-frame-pointer
148
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200149
1502) How to install it
151--------------------
152
153To install haproxy, you can either copy the single resulting binary to the
154place you want, or run :
155
156 $ sudo make install
157
158If you're packaging it for another system, you can specify its root directory
159in the usual DESTDIR variable.
160
161
1623) How to set it up
163-------------------
164
165There is some documentation in the doc/ directory :
166
167 - architecture.txt : this is the architecture manual. It is quite old and
168 does not tell about the nice new features, but it's still a good starting
169 point when you know what you want but don't know how to do it.
170
171 - configuration.txt : this is the configuration manual. It recalls a few
172 essential HTTP basic concepts, and details all the configuration file
173 syntax (keywords, units). It also describes the log and stats format. It
174 is normally always up to date. If you see that something is missing from
175 it, please report it as this is a bug.
176
177 - haproxy-en.txt / haproxy-fr.txt : these are the old outdated docs. You
178 should never need them. If you do, then please report what you didn't
179 find in the other ones.
180
181 - gpl.txt / lgpl.txt : the copy of the licenses covering the software. See
182 the 'LICENSE' file at the top for more information.
183
184 - the rest is mainly for developers.
185
186There are also a number of nice configuration examples in the "examples"
187directory as well as on several sites and articles on the net which are linked
188to from the haproxy web site.
189
190
1914) How to report a bug
192----------------------
193
194It is possible that from time to time you'll find a bug. A bug is a case where
195what you see is not what is documented. Otherwise it can be a misdesign. If you
196find that something is stupidly design, please discuss it on the list (see the
197"how to contribute" section below). If you feel like you're proceeding right
198and haproxy doesn't obey, then first ask yourself if it is possible that nobody
199before you has even encountered this issue. If it's unlikely, the you probably
200have an issue in your setup. Just in case of doubt, please consult the mailing
201list archives :
202
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200203 http://marc.info/?l=haproxy
204
205Otherwise, please try to gather the maximum amount of information to help
206reproduce the issue and send that to the mailing list :
207
208 haproxy@formilux.org
209
210Please include your configuration and logs. You can mask your IP addresses and
211passwords, we don't need them. But it's essential that you post your config if
212you want people to guess what is happening.
213
214Also, keep in mind that haproxy is designed to NEVER CRASH. If you see it die
215without any reason, then it definitely is a critical bug that must be reported
216and urgently fixed. It has happened a couple of times in the past, essentially
217on development versions running on new architectures. If you think your setup
218is fairly common, then it is possible that the issue is totally unrelated.
219Anyway, if that happens, feel free to contact me directly, as I will give you
220instructions on how to collect a usable core file, and will probably ask for
221other captures that you'll not want to share with the list.
222
223
2245) How to contribute
225--------------------
226
227It is possible that you'll want to add a specific feature to satisfy your needs
228or one of your customers'. Contributions are welcome, however I'm often very
229picky about changes. I will generally reject patches that change massive parts
230of the code, or that touch the core parts without any good reason if those
231changes have not been discussed first.
232
233The proper place to discuss your changes is the HAProxy Mailing List. There are
234enough skilled readers to catch hazardous mistakes and to suggest improvements.
Willy Tarreau9a639a12011-09-10 22:48:36 +0200235I trust a number of them enough to merge a patch if they say it's OK, so using
236the list is the fastest way to get your code reviewed and merged. You can
237subscribe to it by sending an empty e-mail at the following address :
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200238
239 haproxy+subscribe@formilux.org
240
Willy Tarreau9a639a12011-09-10 22:48:36 +0200241If you have an idea about something to implement, *please* discuss it on the
242list first. It has already happened several times that two persons did the same
243thing simultaneously. This is a waste of time for both of them. It's also very
244common to see some changes rejected because they're done in a way that will
245conflict with future evolutions, or that does not leave a good feeling. It's
246always unpleasant for the person who did the work, and it is unpleasant for me
247too because I value people's time and efforts. That would not happen if these
248were discussed first. There is no problem posting work in progress to the list,
249it happens quite often in fact. Also, don't waste your time with the doc when
250submitting patches for review, only add the doc with the patch you consider
251ready to merge.
252
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200253If your work is very confidential and you can't publicly discuss it, you can
254also mail me directly about it, but your mail may be waiting several days in
255the queue before you get a response.
256
257If you'd like a feature to be added but you think you don't have the skills to
258implement it yourself, you should follow these steps :
259
260 1. discuss the feature on the mailing list. It is possible that someone
261 else has already implemented it, or that someone will tell you how to
262 proceed without it, or even why not to do it. It is also possible that
263 in fact it's quite easy to implement and people will guide you through
264 the process. That way you'll finally have YOUR patch merged, providing
265 the feature YOU need.
266
267 2. if you really can't code it yourself after discussing it, then you may
268 consider contacting someone to do the job for you. Some people on the
269 list might be OK with trying to do it. Otherwise, you can check the list
270 of contributors at the URL below, some of the regular contributors may
271 be able to do the work, probably not for free but their time is as much
272 valuable as yours after all, you can't eat the cake and have it too.
273
274The list of past and regular contributors is available below. It lists not only
275significant code contributions (features, fixes), but also time or money
276donations :
277
278 http://haproxy.1wt.eu/contrib.html
279
280Note to contributors: it's very handy when patches comes with a properly
Willy Tarreau9a639a12011-09-10 22:48:36 +0200281formated subject. There are 3 criteria of particular importance in any patch :
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200282
Willy Tarreau9a639a12011-09-10 22:48:36 +0200283 - its nature (is it a fix for a bug, a new feature, an optimization, ...)
284 - its importance, which generally reflects the risk of merging/not merging it
285 - what area it applies to (eg: http, stats, startup, config, doc, ...)
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200286
Willy Tarreau9a639a12011-09-10 22:48:36 +0200287It's important to make these 3 criteria easy to spot in the patch's subject,
288because it's the first (and sometimes the only) thing which is read when
289reviewing patches to find which ones need to be backported to older versions.
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200290
Willy Tarreau9a639a12011-09-10 22:48:36 +0200291Specifically, bugs must be clearly easy to spot so that they're never missed.
292Any patch fixing a bug must have the "BUG" tag in its subject. Most common
293patch types include :
294
295 - BUG fix for a bug. The severity of the bug should also be indicated
296 when known. Similarly, if a backport is needed to older versions,
297 it should be indicated on the last line of the commit message. If
298 the bug has been identified as a regression brought by a specific
299 patch or version, this indication will be appreciated too. New
300 maintenance releases are generally emitted when a few of these
301 patches are merged.
302
303 - CLEANUP code cleanup, silence of warnings, etc... theorically no impact.
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200304 These patches will rarely be seen in stable branches, though they
Willy Tarreau9a639a12011-09-10 22:48:36 +0200305 may appear when they remove some annoyance or when they make
306 backporting easier. By nature, a cleanup is always minor.
307
308 - REORG code reorganization. Some blocks may be moved to other places,
309 some important checks might be swapped, etc... These changes
310 always present a risk of regression. For this reason, they should
311 never be mixed with any bug fix nor functional change. Code is
312 only moved as-is. Indicating the risk of breakage is highly
313 recommended.
314
315 - BUILD updates or fixes for build issues. Changes to makefiles also fall
316 into this category. The risk of breakage should be indicated if
317 known. It is also appreciated to indicate what platforms and/or
318 configurations were tested after the change.
319
320 - OPTIM some code was optimised. Sometimes if the regression risk is very
321 low and the gains significant, such patches may be merged in the
322 stable branch. Depending on the amount of code changed or replaced
323 and the level of trust the author has in the change, the risk of
324 regression should be indicated.
325
326 - RELEASE release of a new version (development or stable).
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200327
Willy Tarreau9a639a12011-09-10 22:48:36 +0200328 - LICENSE licensing updates (may impact distro packagers).
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200329
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200330
Willy Tarreau9a639a12011-09-10 22:48:36 +0200331When the patch cannot be categorized, it's best not to put any tag. This is
332commonly the case for new features, which development versions are mostly made
333of.
334
335Additionally, the importance of the patch should be indicated when known. A
336single upper-case word is preferred, among :
337
338 - MINOR minor change, very low risk of impact. It is often the case for
339 code additions that don't touch live code. For a bug, it generally
340 indicates an annoyance, nothing more.
341
342 - MEDIUM medium risk, may cause unexpected regressions of low importance or
343 which may quickly be discovered. For a bug, it generally indicates
344 something odd which requires changing the configuration in an
345 undesired way to work around the issue.
346
347 - MAJOR major risk of hidden regression. This happens when I rearrange
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200348 large parts of code, when I play with timeouts, with variable
349 initializations, etc... We should only exceptionally find such
Willy Tarreau9a639a12011-09-10 22:48:36 +0200350 patches in stable branches. For a bug, it indicates severe
351 reliability issues for which workarounds are identified with or
352 without performance impacts.
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200353
Willy Tarreau9a639a12011-09-10 22:48:36 +0200354 - CRITICAL medium-term reliability or security is at risk and workarounds,
355 if they exist, might not always be acceptable. An upgrade is
356 absolutely required. A maintenance release may be emitted even if
357 only one of these bugs are fixed. Note that this tag is only used
358 with bugs. Such patches must indicate what is the first version
359 affected, and if known, the commit ID which introduced the issue.
360
361If this criterion doesn't apply, it's best not to put it. For instance, most
362doc updates and most examples or test files are just added or updated without
363any need to qualify a level of importance.
364
365The area the patch applies to is quite important, because some areas are known
366to be similar in older versions, suggesting a backport might be desirable, and
367conversely, some areas are known to be specific to one version. When the tag is
368used alone, uppercase is preferred for readability, otherwise lowercase is fine
369too. The following tags are suggested but not limitative :
370
371 - doc documentation updates or fixes. No code is affected, no need to
372 upgrade. These patches can also be sent right after a new feature,
373 to document it.
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200374
Willy Tarreau9a639a12011-09-10 22:48:36 +0200375 - examples example files. Be careful, sometimes these files are packaged.
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200376
Willy Tarreau9a639a12011-09-10 22:48:36 +0200377 - tests regression test files. No code is affected, no need to upgrade.
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200378
Willy Tarreau9a639a12011-09-10 22:48:36 +0200379 - init initialization code, arguments parsing, etc...
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200380
Willy Tarreau9a639a12011-09-10 22:48:36 +0200381 - config configuration parser, mostly used when adding new config keywords
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200382
Willy Tarreau9a639a12011-09-10 22:48:36 +0200383 - http the HTTP engine
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200384
Willy Tarreau9a639a12011-09-10 22:48:36 +0200385 - stats the stats reporting engine as well as the stats socket CLI
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200386
Willy Tarreau9a639a12011-09-10 22:48:36 +0200387 - checks the health checks engine (eg: when adding new checks)
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200388
Willy Tarreau9a639a12011-09-10 22:48:36 +0200389 - acl the ACL processing core or some ACLs from other areas
390
391 - peers the peer synchronization engine
392
393 - listeners everything related to incoming connection settings
394
395 - frontend everything related to incoming connection processing
396
397 - backend everything related to LB algorithms and server farm
398
399 - session session processing and flags (very sensible, be careful)
400
401 - server server connection management, queueing
402
403 - proxy proxy maintenance (start/stop)
404
405 - log log management
406
407 - poll any of the pollers
408
409 - halog the halog sub-component in the contrib directory
410
411 - contrib any addition to the contrib directory
412
413Other names may be invented when more precise indications are meaningful, for
414instance : "cookie" which indicates cookie processing in the HTTP core. Last,
415indicating the name of the affected file is also a good way to quickly spot
416changes. Many commits were already tagged with "stream_sock" or "cfgparse" for
417instance.
418
419It is desired that AT LEAST one of the 3 criteria tags is reported in the patch
420subject. Ideally, we would have the 3 most often. The two first criteria should
421be present before a first colon (':'). If both are present, then they should be
422delimited with a slash ('/'). The 3rd criterion (area) should appear next, also
423followed by a colon. Thus, all of the following messages are valid :
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200424
425Examples of messages :
Willy Tarreau9a639a12011-09-10 22:48:36 +0200426 - DOC: document options forwardfor to logasap
427 - DOC/MAJOR: reorganize the whole document and change indenting
428 - BUG: stats: connection reset counters must be plain ascii, not HTML
429 - BUG/MINOR: stats: connection reset counters must be plain ascii, not HTML
430 - MEDIUM: checks: support multi-packet health check responses
431 - RELEASE: Released version 1.4.2
432 - BUILD: stats: stdint is not present on solaris
433 - OPTIM/MINOR: halog: make fgets parse more bytes by blocks
434 - REORG/MEDIUM: move syscall redefinition to specific places
435
436Please do not use square brackets anymore around the tags, because they give me
437more work when merging patches. By default I'm asking Git to keep them but this
438causes trouble when patches are prefixed with the [PATCH] tag because in order
439not to store it, I have to hand-edit the patches. So as of now, I will ask Git
440to remove whatever is located between square brackets, which implies that any
441subject formatted the old way will have its tag stripped out.
442
443In fact, one of the only square bracket tags that still makes sense is '[RFC]'
444at the beginning of the subject, when you're asking for someone to review your
445change before getting it merged. If the patch is OK to be merged, then I can
446merge it as-is and the '[RFC]' tag will automatically be removed. If you don't
447want it to be merged at all, you can simply state it in the message, or use an
448alternate '[WIP]' tag ("work in progress").
449
450The tags are not rigid, follow your intuition first, anyway I reserve the right
451to change them when merging the patch. It may happen that a same patch has a
452different tag in two distinct branches. The reason is that a bug in one branch
453may just be a cleanup in the other one because the code cannot be triggered.
454
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200455
456For a more efficient interaction between the mainline code and your code, I can
457only strongly encourage you to try the Git version control system :
458
459 http://git-scm.com/
460
461It's very fast, lightweight and lets you undo/redo your work as often as you
462want, without making your mistakes visible to the rest of the world. It will
463definitely help you contribute quality code and take other people's feedback
464in consideration. In order to clone the HAProxy Git repository :
465
466 $ git clone http://git.1wt.eu/git/haproxy-1.4.git (stable 1.4)
467 $ git clone http://git.1wt.eu/git/haproxy.git/ (development)
468
Willy Tarreau663148c2012-12-12 00:38:22 +0100469The site above is slow, a faster mirror is maintained up to date here :
470
471 $ git clone http://master.formilux.org/git/people/willy/haproxy.git/
472
Willy Tarreaub1a34b62010-05-09 22:37:12 +0200473If you decide to use Git for your developments, then your commit messages will
474have the subject line in the format described above, then the whole description
475of your work (mainly why you did it) will be in the body. You can directly send
476your commits to the mailing list, the format is convenient to read and process.
477
willy tarreau78345332005-12-18 01:33:16 +0100478-- end