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

akitouni pushed a change to branch abderrahim/cargo-fixes
in repository https://gitbox.apache.org/repos/asf/buildstream-plugins.git


 discard db6da4c  cargo: don't subscript node instances
 discard cf08d80  Fix running track multiple times with cargo plugin
 discard ab8f18a  cargo: don't download crates at track time if the checksums 
are available in the lock file
 discard 4ed45b3  cargo: Fix tracking with aliases and no refs
     new df490e1  cargo: don't subscript node instances
     new 5e1b22c  cargo: Fix tracking with aliases and no refs
     new 00d876f  cargo: don't download crates at track time if the checksums 
are available in the lock file
     new 560bdca  cargo: Fix running track multiple times with cargo plugin

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   (db6da4c)
            \
             N -- N -- N   refs/heads/abderrahim/cargo-fixes (560bdca)

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 4 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:

Reply via email to