# C:\Foo\Bar\my_script.pl use strict; use warnings; use FindBin qw($Bin); print "My script lives in $Bin\n"; # My script lives in C:/Foo/Bar
Note that there is no trailing slash, and Windows back-slashes '\' are converted to forward slashes '/'
# C:\Foo\Bar\my_script.pl use strict; use warnings; use FindBin qw($Bin); print "My script lives in $Bin\n"; # My script lives in C:/Foo/Bar
Let's say you have these N successive commits: 1, 2, 3 and 4.If you select the commit 2 and choose "Revert to this revision", your working copy will contain the changes brought by commits 1 and 2. Commits 3 and 4 will be "canceled".If you select the commit 2 and choose "Revert changes from this revision", your working copy will contain the changes brought by commits 1, 3 and 4. Commit 2 will be "canceled", or rather, played in reverse on the top of commit 4: if a line was added, it will be removed. If a line was removed, it will be re-added.
Update to revision will only update files of your working copy to your chosen revision. But you cannot continue to work on this revision, as SVN will complain that your working copy is out of date.revert to this revision will undo all changes in your working copy which were made after the selected revision (in your example rev. 96,97,98,99,100) Your working copy is now in modified state.The file content of both scenarios is same, however in first case, you have an unmodified working copy and you cannot commit your changes (as your working copy is not pointing to HEAD rev 100), in second case you have a modified working copy pointing to head and you can continue to work and commit
my ($match) = "some string" =~ /(some).*/; print $match; # prints "some"