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

juergbi pushed a change to branch jbilleter/checkout
in repository https://gitbox.apache.org/repos/asf/buildstream.git


 discard 89c3b2f80 cascache.py: Replace existing files in `checkout` for 
symlinks
 discard 3716916f3 cascache.py: Ensure that `checkout()` doesn't follow 
directory symlinks
 discard 0b6c28329 _casbaseddirectory.py: Detect duplicate `Directory` node 
names
 discard 152b9fce2 cascache.py: Detect duplicate `Directory` node names
     new 098f3dc7d cascache.py: Detect duplicate `Directory` node names
     new d0b124d0e _casbaseddirectory.py: Detect duplicate `Directory` node 
names
     new 243174d61 cascache.py: Ensure that `checkout()` doesn't follow 
directory symlinks
     new 43b2292f0 cascache.py: Replace existing files in `checkout` for 
symlinks

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   (89c3b2f80)
            \
             N -- N -- N   refs/heads/jbilleter/checkout (43b2292f0)

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:
 src/buildstream/_cas/cascache.py              | 4 ++--
 src/buildstream/storage/_casbaseddirectory.py | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

Reply via email to