This is an automated email from the ASF dual-hosted git repository.
reiern70 pushed a change to branch WICKET-6878
in repository https://gitbox.apache.org/repos/asf/wicket.git.
discard 1a6055e [WICKET-6876] fix JS to make build pass
discard aa138c9 [WICKET-6876] add factory methods
discard 046bfe1 [WICKET-6876] add factory methods
discard b4d7da9 [WICKET-6876] add an AJAX behavior to transfer client side
files information to server side (when a file/files is/are selected for upload
at client side).
add 048e568 WICKET-6875 Example for FileSystemResource.java does not work
add 2dd9bf8 [WICKET-6876] add an AJAX behavior to transfer client side
files information to server side (when a file/files is/are selected for upload
at client side).
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 (1a6055e)
\
N -- N -- N refs/heads/WICKET-6878 (2dd9bf8)
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:
.../java/org/apache/wicket/resource/FileSystemResourceReference.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
