This is an automated email from the ASF dual-hosted git repository.
reiern70 pushed a change to branch reiern70/WICKET-7033
in repository https://gitbox.apache.org/repos/asf/wicket.git
discard 9dcdc8ccea [WICKET-7033] WIP
discard ccb31a5bf3 [WICKET-7033] WIP
discard ff30454860 [WICKET-7033] WIP
discard 351802069e [WICKET-7033] WIP
discard 9d162710af [WICKET-7033] WIP
discard 04c838f0d7 [WICKET-7033] WIP
discard aab23d5752 [WICKET-7033] WIP
new b3df5eeef4 [WICKET-7033] prototype implementation of uploading file to
a resource
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 (9dcdc8ccea)
\
N -- N -- N refs/heads/reiern70/WICKET-7033 (b3df5eeef4)
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 1 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:
