This is an automated email from the ASF dual-hosted git repository.
reiern70 pushed a change to branch upload-to-resource
in repository https://gitbox.apache.org/repos/asf/wicket.git
omit 1824d004c5 Make the deprecated IUploadsFileManager#save() fail clearly
instead of calling store()
omit 5bca4b00e1 Describe the migration of uploads to a resource to Wicket 11
omit 79afd1d3b3 Explain the limits and the files of one name in the
upload-to-resource example
omit 12e4ab5a93 Test the paths of uploads to a resource that no test reached
omit bd2441e2cc Wrap the QUnit tests of uploads to a resource in a function
omit 1603b49ed2 Word a lost connection of an upload to a resource, and let
subclasses word upload errors
omit 3842cb78f8 Add a drop zone and a file list to uploads to a resource
omit a75841a9de Make uploads to a resource fail cleanly and keep files of
one name apart
add a7f933a1b6 Make uploads to a resource fail cleanly and keep files of
one name apart
add 208e96335b Add a drop zone and a file list to uploads 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 (1824d004c5)
\
N -- N -- N refs/heads/upload-to-resource (208e96335b)
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:
