On 06/04/2020 13:28, Cantor, Scott wrote:
On 4/6/20, 8:24 AM, "Roger Leigh" wrote:
It should be pretty simple for any Apache contributor to push any
potential update as a feature branch to GitBox and then check the CI run
passes, prior to merging to an integration branch. This will ensure
On 4/6/20, 8:24 AM, "Roger Leigh" wrote:
> It should be pretty simple for any Apache contributor to push any
> potential update as a feature branch to GitBox and then check the CI run
> passes, prior to merging to an integration branch. This will ensure
> that no regressions should be
On 06/04/2020 12:42, Cantor, Scott wrote:
On 4/6/20, 7:21 AM, "Roger Leigh" wrote:
You can simply push your feature branch and wait for the tests to pass before
merging to and pushing the integration
branch.
I'm not sure that there's been adequate discussion of any actual development
alexeyroytman closed pull request #3: XERCESC-2185 XERCESC-2186 XERCESC-2187 -
Solaris, HP-UX and AIX
URL: https://github.com/apache/xerces-c/pull/3
This is an automated message from the Apache Git Service.
To respond to
viniul commented on issue #2: Commit fuzzer source code.
URL: https://github.com/apache/xerces-c/pull/2#issuecomment-609751899
Got it, will keep that in mind. Thank you very much - I will work on the
changes to the configure script and post a link to the jira ticket here as soon
as I am
scantor commented on issue #2: Commit fuzzer source code.
URL: https://github.com/apache/xerces-c/pull/2#issuecomment-609751003
Just minimizing the impact on the configure script, so I can avoid having to
do too much integration testing/review, but otherwise since all the code you're
viniul commented on issue #2: Commit fuzzer source code.
URL: https://github.com/apache/xerces-c/pull/2#issuecomment-609750093
Absolutely! Anything else we can do on our side to make this integration as
easy as possible?
scantor commented on issue #2: Commit fuzzer source code.
URL: https://github.com/apache/xerces-c/pull/2#issuecomment-609749663
That clarifies things, thank you. I'm not opposed, but you can save me some
time by attaching the patch to a JIRA ticket (there may be one already for your
viniul commented on issue #2: Commit fuzzer source code.
URL: https://github.com/apache/xerces-c/pull/2#issuecomment-609748766
You are right, the current PR does not make any changes to the Makefile -
that was a mistake on our part, thank you for pointing that out. We will add
another
Cogitri commented on issue #8: cmake: use HAVE_SIZE_OF_S{,S}IZE_T to check if
it's available
URL: https://github.com/apache/xerces-c/pull/8#issuecomment-609744515
aacdef3fa74bea84ff1ff4cd699782bcc080873f
This is an automated
Cogitri closed pull request #8: cmake: use HAVE_SIZE_OF_S{,S}IZE_T to check if
it's available
URL: https://github.com/apache/xerces-c/pull/8
This is an automated message from the Apache Git Service.
To respond to the
On 4/6/20, 7:21 AM, "Roger Leigh" wrote:
> You can simply push your feature branch and wait for the tests to pass
> before merging to and pushing the integration
> branch.
I'm not sure that there's been adequate discussion of any actual development
process for using git, or any policies put
scantor commented on issue #2: Commit fuzzer source code.
URL: https://github.com/apache/xerces-c/pull/2#issuecomment-609742281
It appears this is code that isn't part of the actual build (no makefile
changes), so what's the significance of this being in the distribution? Seems
like
scantor commented on issue #3: XERCESC-2185 XERCESC-2186 XERCESC-2187 -
Solaris, HP-UX and AIX
URL: https://github.com/apache/xerces-c/pull/3#issuecomment-609740629
Don't have access but this should be closed.
This is an
scantor commented on issue #8: cmake: use HAVE_SIZE_OF_S{,S}IZE_T to check if
it's available
URL: https://github.com/apache/xerces-c/pull/8#issuecomment-609740425
Don't have access but this should be closed.
This is an
Dear all,
CI testing was present prior to the switch from SVN to GitBox, but
needed re-enabling by Infra for the new repository. It's re-enabled
since yesterday (see INFRA-20073), and both the xerces-3.2 and master
branch are passing for both Travis and AppVeyor:
This is an automated email from the ASF dual-hosted git repository.
rleigh pushed a change to branch ci-test
in repository https://gitbox.apache.org/repos/asf/xerces-c.git.
omit 03fee10 Merge pull request #9 from
rleigh-codelibre/cmake-libname-fixes
omit 84395e5 cmake: Correct shared
This is an automated email from the ASF dual-hosted git repository.
rleigh pushed a change to branch ci-test
in repository https://gitbox.apache.org/repos/asf/xerces-c.git.
at 03fee10 Merge pull request #9 from
rleigh-codelibre/cmake-libname-fixes
No new revisions were added by this
18 matches
Mail list logo
