This is an automated email from the ASF dual-hosted git repository.
omalley pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/orc.git.
discard cc7810e Merge pull request #325 from dongjoon-hyun/ORC-413-3
omit 593daee ORC-419: Ensure to call `close` at RecordReaderImpl
constructor exception
omit 51084c8 Merge pull request #323 from apache/revert-322-ORC-419
omit ee41fff Revert "ORC-419: Ensure to call `close` at RecordReaderImpl
constructor exception"
omit 9b12616 Merge pull request #322 from dongjoon-hyun/ORC-419
omit d68bd11 ORC-419: Ensure to call `close` at RecordReaderImpl
constructor exception
new 786fd3e ORC-419: Ensure to call `close` at RecordReaderImpl
constructor exception
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (cc7810e)
\
N -- N -- N refs/heads/master (786fd3e)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
