Checkout menu item missing bug, and a couple questions
From: M.Z. <Ziggyesque_at_hotmail.com>
Date: Tue, 11 Nov 2008 16:27:25 -0500
Thank you for the quick reply, Stefan. Reply interleaved below.
--- > > branches subdirs. > To cherry pick other folders for checkout: > * right-click on the checked out folder > * choose "repository browser" from the menu > * select the folder you want to add > * right-click, choose "checkout" Tried that, sometimes errors out with directory not empty type of errors, and doesn't have the same default dirs behavior as the WC side commands do. I haven't saved exact occurrence data so won't file a specific bug report on that. Besides, that's more a workaround, IMO, than what someone could reasonably expect to see as the behavior of the explorer right-click menu now that the depth option is there. When depth<full and sub-directories are available in the repository that haven't been checked out for the first time, personally I'd expect to use Checkout to get them, and the command showing up would be an implicit reminder that the directory is still a sparse one, or that new subdirectories or files are available. Also, when depth < full, I'd expect that the basic Update command behaves like Update to Revision/ Working Copy, recursing into just what subdirectories are already there, and doing a full update of the files, if needed and depth>empty. > > Any possibility the Checkout and Update to Revision ops can be modified --- > > request to the repository, as it appears to be implemented now. > That's the behavior of the svn library. You'd have to ask for this on > the Subversion mailing list. I figure since you have the browser code, and the SVN repo doesn't, it would be easier for you to graft a prototype into the TortoiseProc command handlers in a block like: if repo-dir-from-dialog-or-admin-dir-exists && depth <> full { if query-repo-version < 1.5 { do repo-browse-logic dirs and files/files only checkout or update } else { keep current methods } } and into TortoiseShell for the extended Checkout visibility changes. Where it would go in SVN more problematic: libsvn, wc, ra, or the svn app; all or some of these needing modifying, or more? If you got the change working in TSVN it would make it easier to decide how best to retrofit it into the command-line clients, I'd think. Bass-ackwards, I agree, but can consider it a temporary proof-of-concept kludge than the actual permanent implementation. > Stefan Mark -- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org For additional commands, e-mail: users-help_at_tortoisesvn.tigris.orgReceived on 2008-11-11 22:29:23 CET |
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.