This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/filebaseddirectory
in repository https://gitbox.apache.org/repos/asf/buildstream.git
omit 5123af1e0 _filebaseddirectory.py: Improve checks in `open_file()`
omit d79c725b9 _filebaseddirectory.py: Don't let `utime()` follow symlinks
omit e5bed2953 _filebaseddirectory.py: Fix `import_single_file()`
add 6e8502617 _filebaseddirectory.py: Minor fix for directory symlink
add 2d2387c33 _filebaseddirectory.py: Fix `import_single_file()`
add a9769a1a4 _filebaseddirectory.py: Don't let `utime()` follow symlinks
add 5310ffed8 _filebaseddirectory.py: Improve checks in `open_file()`
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 (5123af1e0)
\
N -- N -- N refs/heads/jbilleter/filebaseddirectory (5310ffed8)
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/storage/_filebaseddirectory.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
