[avro] branch avro-3630-append-to-preexisting-bytes updated (c0b0bf320 -> a5aa80fd3)

[mg...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mgrigorov pushed a change to branch avro-3630-append-to-preexisting-bytes
in repository https://gitbox.apache.org/repos/asf/avro.git


 discard c0b0bf320 AVRO-3630: [Rust] Make it possible to extend pre-existing Avro bytes
     add 14db7b75f Bump thiserror from 1.0.35 to 1.0.36 in /lang/rust (#1891)
     add e949af01d Bump syn from 1.0.100 to 1.0.101 in /lang/rust (#1890)
     add 2c188b3a6 Bump proc-macro2 from 1.0.43 to 1.0.44 in /lang/rust (#1889)
     add a5aa80fd3 AVRO-3630: [Rust] Make it possible to extend pre-existing Avro bytes

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   (c0b0bf320)
            \
             N -- N -- N   refs/heads/avro-3630-append-to-preexisting-bytes (a5aa80fd3)

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.

No new revisions were added by this update.

Summary of changes:
 lang/rust/Cargo.lock             | 16 ++++++++--------
 lang/rust/avro/Cargo.toml        |  2 +-
 lang/rust/avro_derive/Cargo.toml |  4 ++--
 3 files changed, 11 insertions(+), 11 deletions(-)