pull request to add support for Bitrig

[Dave Huseby]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Bitrig just released released their 1.0.  It is in use in the wild, so
I believe it is worth merging this.

I ported Rust to Bitrig and originally submitted this patch to the
Rust team's fork of jemalloc.  They suggested that I upstream it since
jemalloc is used for other things (e.g. Firefox).

My Bitrig Rust port just landed two days ago:

https://github.com/rust-lang/rust/commit/551304015bac6f8424fcc6827855d3c61fe167c9

- --dave

On 02/18/2015 09:28 PM, Jason Evans wrote:
> On Feb 17, 2015, at 1:00 PM, Dave Huseby <dave at linuxprogrammer.org>
> wrote:
>> I just submitted a pull request to add support for building
>> jemalloc on Bitrig:
>> 
>> https://github.com/jemalloc/jemalloc/pull/194
>> 
>> Is that the best/easiest way to get a patch landed?  If not, how
>> should I submit the change?
> 
> Yes, your pull request was the optimal submission mechanism.  I got
> hung up trying to figure out what Bitrig is, whether it is in use
> in the wild, etc.  Is it in a state that justifies merging
> support?
> 
> Thanks, Jason
> 
-----BEGIN PGP SIGNATURE-----

iF4EAREIAAYFAlTryicACgkQvt/JvmUQuOlpVgD+MCHXBj1MNBp3T8+Qh+N6VYOK
JBpv69FtB3BJK/3cBrYA/iGSf1XR2KxLn9/zupats5xZmZQinJRle1DvMXZD3ssH
=SwV5
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x6510B8E9.asc
Type: application/pgp-keys
Size: 30390 bytes
Desc: not available
URL: <http://jemalloc.net/mailman/jemalloc-discuss/attachments/20150223/9f171880/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x6510B8E9.asc.sig
Type: application/pgp-signature
Size: 96 bytes
Desc: not available
URL: <http://jemalloc.net/mailman/jemalloc-discuss/attachments/20150223/9f171880/attachment-0001.sig>