On 26/08/2020 18:43, Christopher Schultz wrote:
> Is there a particular reason we don't just shade the commons-dbcp and
> commons-pool code at build-time rather than manually merging-in
> patches to our private copy?
The short answer is greater flexibility.
The longer answer is that there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 8/26/20 13:36, Mark Thomas wrote:
> On 26/08/2020 17:56, Christopher Schultz wrote:
>> Mark,
>>
>> On 8/26/20 11:19, ma...@apache.org wrote:
>>> This is an automated email from the ASF dual-hosted git
>>> repository.
>>
>>> markt pushed a c
On 26/08/2020 17:56, Christopher Schultz wrote:
> Mark,
>
> On 8/26/20 11:19, ma...@apache.org wrote:
>> This is an automated email from the ASF dual-hosted git
>> repository.
>
>> markt pushed a commit to branch master in repository
>> https://gitbox.apache.org/repos/asf/tomcat.git
>
>> commit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 8/26/20 11:19, ma...@apache.org wrote:
> This is an automated email from the ASF dual-hosted git
> repository.
>
> markt pushed a commit to branch master in repository
> https://gitbox.apache.org/repos/asf/tomcat.git
>
> commit f1c4210470a2
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit 27f81e4fe98725c85a9d0b8411a056b95dca9cd9
Author: Mark Thomas
AuthorDate: Wed Aug 26 16:15:50 2020 +0100
Update Common
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit 6c17d912913502eb4f92461e24e31dda80086aaa
Author: Mark Thomas
AuthorDate: Wed Aug 26 16:15:50 2020 +0100
Update Common
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit f1c4210470a268ec6830a95ab219f418a7e775fb
Author: Mark Thomas
AuthorDate: Wed Aug 26 16:15:50 2020 +0100
Update Commo
