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

juergbi pushed a change to branch juerg/junction-aliases
in repository https://gitbox.apache.org/repos/asf/buildstream.git


 discard 3d210e3c7 doc: Document `disallow-subproject-uris`
 discard 05d4c14fb fixup! fixup! Support mapping subproject aliases to aliases 
of the parent project
     add 76a7cc456 WIP: Add test for the subproject alias functionality
     new 73e19d482 fixup! fixup! Support mapping subproject aliases to aliases 
of the parent project
     new e7193129c doc: Document `disallow-subproject-uris`
     new 77b86aa76 _project.py: Let `disallow-subproject-uris` imply fatal 
`unaliased-url`
     new 9ee4b817f fixup! WIP: Add test for the subproject alias functionality

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   (3d210e3c7)
            \
             N -- N -- N   refs/heads/juerg/junction-aliases (9ee4b817f)

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/_project.py |  5 +++
 tests/frontend/mirror.py    | 92 +++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 97 insertions(+)

Reply via email to