-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/18/2015 09:30 AM, Drew Wells wrote:
> On 09/18/2015 03:23 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> Applies perfectly! Thanks!
>>
>> On 09/18/2015 09:21 AM, Drew Wells wrote:
>>> On 09/18/2015 02:47 PM, M
On 09/18/2015 03:23 PM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applies perfectly! Thanks!
On 09/18/2015 09:21 AM, Drew Wells wrote:
On 09/18/2015 02:47 PM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Drew, I know you've put a lot of effor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applies perfectly! Thanks!
On 09/18/2015 09:21 AM, Drew Wells wrote:
> On 09/18/2015 02:47 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> Drew, I know you've put a lot of effort into these patches, but they do not
On 09/18/2015 02:47 PM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Drew, I know you've put a lot of effort into these patches, but they do not
succeed against the
5.5.0 trunk. Patches should be made against the most recent revision, which
can be checked out via
Subver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Drew, I know you've put a lot of effort into these patches, but they do not
succeed against the
5.5.0 trunk. Patches should be made against the most recent revision, which
can be checked out via
Subversion from Sourceforge.
On 09/18/2015 08:11 AM,
On 09/17/2015 04:55 PM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/17/2015 10:52 AM, Drew Wells wrote:
I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to
5.5.0, some of it
had already been done to 5.5.0 and alot of it centered around the sn
On 09/17/2015 04:55 PM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/17/2015 10:52 AM, Drew Wells wrote:
I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to
5.5.0, some of it
had already been done to 5.5.0 and alot of it centered around the sn
