This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/virtual-directory-cleanup
in repository https://gitbox.apache.org/repos/asf/buildstream.git.
discard 066ad9e storage/_filebaseddirectory.py: Public/Private split + type
annotations
discard e48a84a storage: Raise only DirectoryError from Directory backends
add 5fb5f0a storage: Raise only DirectoryError from Directory backends
add fe79e9f storage/_filebaseddirectory.py: Public/Private split + type
annotations
add fae0c1e storage/directory.py: Implement our own FileStat
add a929cdd storage/directory.py: Added listdir() method
add 077a044 storage/_filebaseddirectory.py: Implement import_files()
without importing CasBasedDirectory
add e9a2f41 storage/directory.py: Remove "report_written" from
Directory.import_files()
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 (066ad9e)
\
N -- N -- N refs/heads/tristan/virtual-directory-cleanup
(e9a2f41)
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:
src/buildstream/element.py | 2 +-
src/buildstream/storage/_casbaseddirectory.py | 49 +++---
src/buildstream/storage/_filebaseddirectory.py | 234 +++++++++++++------------
src/buildstream/storage/directory.py | 80 +++++++--
tests/internals/storage.py | 15 +-
5 files changed, 222 insertions(+), 158 deletions(-)
