Re: This recipe:
>
* checkout MyHeadDirectory with depth "only file children"
* open repository browser on checked out working copy
* browse to Subdirectory1, right-click, "update item to revision",
select depth "fully recursive"
* repeat for Subdirectory3
Stefan
>
The bug is: In the Repo Browser the same logic for staging Checkouts
on multiple selected subdirectories isn't used when all the subdirs
selected are also Update To Revision candidates. Also, the menu item
for Update To is active when you select multiples in the Explorer file
pane, including a mix of dirs and files, so this is inconsistent
behavior between the two. If the logic for the staging is in there, it
could be simply the checks needed to undisable the menu item for this
case aren't there.
Fixing this, you'd only need one TortoiseProc session to grab multiple
tags or branches of interest, and they'd all have the same rev number.
On some large repositories you can have 3 or 4 commits to various
parts of it in the time it takes to do a relatively small checkout, so
it takes a final Update To Revision/ Working Copy from Explorer to get
all the individual checkouts to the same Rev level.
This would change the recipe to:
* checkout MyHeadDirectory with depth "only file children"
* open repository browser on checked out working copy
* browse to Parent of Subdirectory1 in dir tree, select Subdirectory1
in file pane
* Ctrl-Click Subdirectory3, 6, 15, 137, etc.
* right-click on a selected item, "update item to revision", select
depth other than Working Copy
* Wait for TortoiseProc to run once
Also, since Working Copy does only apply to items already checked out,
for sparse checkouts like this, the option should be removed from the
depth choices combo box, as it's a no-op. At the least, it should not
be the default selection there; Dirs Only or Fully Recursive should
be. Since there aren't that many selections anyways, changing the
combo box to a radio button group wouldn't expand the dialog's
dimensions significantly, and it would both save the extra click on
the drop down arrow and let you disable choices individually.
A simple scenario for multiple disables being desirable is: when you
only have a file or files selected in the browser the only depth that
makes sense is Files Only, and the rest can be grayed out. This
provides immediate visual feedback on the possibilities appropriate to
what has been selected. That's the feature request. It also applies to
the Checkout dialog, I'd think. :-) I also think there are some
missing depth choices, related to working copy state from prior sparse
checkouts and not just this simple case, but that's a whole other
kettle of fish to stew over as a BIG bug report on the SVN list, most
likely.
Cheers,
Mark
On May 3, 2:53 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> Ronni Rosenberg wrote:
> > Let me be more specific. I have the following structure:
>
> > MyHeadDirectory
> > Subdirectory1
> > Subdirectory2
> > Subdirectory3
>
> > (The subdirectories have their own subdirectories in turn.)
>
> > I want to delete my working copy of Subdirectory2. Then, when I do
> > future updates at the level of MyHeadDirectory, I want to get only
> > Subdirectory1 and Subdirectory3. Is this doable?
>
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2047638
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-03 19:31:45 CEST