Can I present the tool for image comparison for all of svn users?
Can I present the tool for image comparison for all of svn users? I have simple tool for comparing images, with support for wide list of graphic formats, including PSD, SVG and MS Visio VSD. It can run from command-line or from your favorite client. http://soft.postpdm.com/cad_diff.html Program is free and portable. Thank you! --- Yuri http://soft.postpdm.com/
Re: SVN copy multiple files
Sorry, I misread your question (I read --parents instead of --targets ... must have my eyes checked ;-). -- Johan On Mon, Dec 5, 2016 at 2:38 PM, Campbell, Nina wrote: > Thanks for your response. I am already handling the intermediate directories, > the issue I'm having is copying multiple files to a URL in the same revision > without having to put all of their paths on the command line. Sorry if I was > unclear! (I mentioned --targets as an example because it allows the user to > operate on a single file containing all of the desired files' paths.) > > Cheers. > > From: Johan Corveleyn [mailto:jcor...@gmail.com] >> 'svn copy' does have a --parents option (introduced in 1.8 or 1.9, I'm not >> sure): > >> [[[ >> C:\>svn help copy >> copy (cp): Copy files and directories in a working copy or repository. >> usage: copy SRC[@REV]... DST > >> SRC and DST can each be either a working copy (WC) path or URL: >>WC -> WC: copy and schedule for addition (with history) >> WC -> URL: immediately commit a copy of WC to URL >> URL -> WC: check out URL into WC, schedule for addition >> URL -> URL: complete server-side copy; used to branch and tag >> All the SRCs must be of the same type. When copying multiple sources, >> they will be added as children of DST, which must be a directory. > >>... > >> --parents: make intermediate directories >> ]]]
RE: SVN copy multiple files
Thanks for your response. I am already handling the intermediate directories, the issue I'm having is copying multiple files to a URL in the same revision without having to put all of their paths on the command line. Sorry if I was unclear! (I mentioned --targets as an example because it allows the user to operate on a single file containing all of the desired files' paths.) Cheers. From: Johan Corveleyn [mailto:jcor...@gmail.com] > 'svn copy' does have a --parents option (introduced in 1.8 or 1.9, I'm not > sure): > [[[ > C:\>svn help copy > copy (cp): Copy files and directories in a working copy or repository. > usage: copy SRC[@REV]... DST > SRC and DST can each be either a working copy (WC) path or URL: >WC -> WC: copy and schedule for addition (with history) > WC -> URL: immediately commit a copy of WC to URL > URL -> WC: check out URL into WC, schedule for addition > URL -> URL: complete server-side copy; used to branch and tag > All the SRCs must be of the same type. When copying multiple sources, > they will be added as children of DST, which must be a directory. >... > --parents: make intermediate directories > ]]]
RE: SVN copy multiple files
From: Pavel Lyalyakin [mailto:pavel.lyalya...@visualsvn.com] > Have you tried `svnmucc` Subversion Multiple URL Command Client? > http://svnbook.red-bean.com/en/1.8/svn.ref.svnmucc.re.html Thank you, I hadn't heard of svnmucc. I've taken a look and I can see the advantages of it when doing multiple operations (e.g. delete, copy, then move), but if I'm just copying files I don't see how it differs from doing "svn copy file1 file2 file3 [...] DEST_URL"? I was hoping for a method that didn't require putting all of the file paths on the same command line (because they are very long, and a large number of files might be selected). This is why --targets was so useful when committing files, because I could write all of the file paths to a .txt beforehand and then just operate on that .txt. Thanks for the help.
Re: SVN copy multiple files
On Mon, Dec 5, 2016 at 12:48 PM, Campbell, Nina wrote: ... > For committing files in a single revision I use --targets but there doesn’t > seem to be a ‘copy’ equivalent of this command. Am I missing something > obvious? 'svn copy' does have a --parents option (introduced in 1.8 or 1.9, I'm not sure): [[[ C:\>svn help copy copy (cp): Copy files and directories in a working copy or repository. usage: copy SRC[@REV]... DST SRC and DST can each be either a working copy (WC) path or URL: WC -> WC: copy and schedule for addition (with history) WC -> URL: immediately commit a copy of WC to URL URL -> WC: check out URL into WC, schedule for addition URL -> URL: complete server-side copy; used to branch and tag All the SRCs must be of the same type. When copying multiple sources, they will be added as children of DST, which must be a directory. ... --parents: make intermediate directories ]]] -- Johan
Re: SVN copy multiple files
Hello Nina, On Mon, Dec 5, 2016 at 2:48 PM, Campbell, Nina wrote: > Is there a way to copy multiple files from WC to URL in one revision? In my > current setup I am copying files from the working copy to a repository URL, > so the copy is immediately committed. These files can be in multiple > directories. However this means the target repository’s revision number is > incremented per file. Have you tried `svnmucc` Subversion Multiple URL Command Client? http://svnbook.red-bean.com/en/1.8/svn.ref.svnmucc.re.html -- With best regards, Pavel Lyalyakin VisualSVN Team
SVN copy multiple files
Is there a way to copy multiple files from WC to URL in one revision? In my current setup I am copying files from the working copy to a repository URL, so the copy is immediately committed. These files can be in multiple directories. However this means the target repository's revision number is incremented per file. The only suggested solutions I've found seem to be: 1) Put all of the files on the command line together (e.g. "svn copy file1 file2 file3 destination_URL") however I need to provide support for a large number of files with long paths 2) Copy the files individually and then do one commit, however in my case I need to allow the user to copy files to a repository they don't have a working copy for 3) Create a temporary working copy directory, copy all of the files there, and then copy that directory to tag. I'd rather not clog up the working copy repository's log with committing and deleting temp files that are being copied to tag For committing files in a single revision I use --targets but there doesn't seem to be a 'copy' equivalent of this command. Am I missing something obvious? Thanks in advance.
Re: Corrupted Repo From Deleting Directory
Hello Shira, You emailed dev@ TortosieSVN mailing list dedicated to the discussion of TortoiseSVN development. That's why this is not the right place for asking user support. Use users@ list instead and read the Community page: https://tortoisesvn.net/community.html I'm removing dev@ and adding @users. On Fri, Dec 2, 2016 at 11:24 PM, Shira Hammann wrote: > > I'm hoping folks may have some guidance on how to stop my repo from getting > corrupted by folder deletes. I guess that by "repo" you mean "working copy" (https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-basics-svn.html#tsvn-basics-svn-workingcopy). Right? Do you store the working copy on local computer or on a network share? > > Since I started using tortoisesvn 3 months ago, my repo has twice been > corrupted so that I had to delete it and check out the code from scratch. > Both times, this has occurred when I attempted to delete a directory in the > repo. > > The first time, I just physically deleted the directory using FileExplorer. > One of my colleagues says he does this all the time and it works fine with > the same versions of svn and tortoisesvn that I'm using. I no longer remember > all the details of the errors I got, but I know that my repo ended up > corrupted and Clean up didn't work and I ended up having to get the repo > again. All those details are essential to provide advise or suggestions. Please, specify the exact and complete wordings of the errors you receive and a brief summary of actions you did prior the error occured. Note that the state of a working copy that requires a clean up, does not mean that the working copy is corrupted or anything. A clean up might be required in case your working copy is in inconsistent state. This could happen, for example, in case you cancel SVN operation that's in progress. Read https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-cleanup.html and http://svnbook.red-bean.com/en/1.8/svn.tour.cleanup.html > > This time, I right clicked the directory, and chose TortoiseSVN -> Delete. > Just prior to doing that, I had gone to the SVN Commit page from my project > root, and it looked fine. However, after deleting a directory a couple of > levels down, the SVN Commit page no longer found any pending changes. That > was true whether I tried from the root or from a subdirectory that didn't > contain the deleted directory. I then tried to do a Clean up, again trying > from both of the same locations, and it failed saying "Cleanup failed to > process the following path:", then the path of the directory I'm trying to > clean, then "Can't open directory", then the path of the directory I had > deleted, then "Access is denied." I'm totally confused. Why do you run `svn delete`? What was the output of `svn status --verbose`? What made you think that you should run `svn delete` command? BTW, "Access is denied" is still just "Access is denied". You should double-check that your Windows / AD user account has full Read Write access to the location of your working copies. There is a chance that the errors occur due to lack of permissions. What about checking out the working copies to a new location where you sure have full access permissions? > > At this point I have no idea how to fix the issue, so I'm getting a brand new > copy of the repo. However, this is a frustrating thing to have happen every > time I need to delete a directory and I'm hoping folks may have run into the > same and be able to suggest a better option. I would suggest reading the documentation http://svnbook.red-bean.com/en/1.8/svn.tour.html & https://tortoisesvn.net/docs/release/TortoiseSVN_en/index.html Sorry, but I'm not sure what kind of issue you are trying to describe. Some error messages and a reproduction script could help. -- With best regards, Pavel Lyalyakin VisualSVN Team
