Suggestion for improved use of cvs checkout to update sandboxes

When working with virtual modules, the best way to update your sandbox 
is to use cvs checkout instead of cvs update, so you get any newly 
added directories which belong to the virtual module.
However, doing so is a little cumbersome as you have to enter the 
module name each time (or at least bring up the checkout dialog, check 
your settings, etc.).

My suggestion would be to remember the module name when doing a 
checkout (e.g. in an invisible file at the top level of the sandbox) 
and provide a command to update the existing sandbox using "checkout" 
when
	(a) only the top level sandbox folder is selected (or nothing is 
selected) and
	(b) that invisible file exists at this level

That way, updating a sandbox for a virtual module would be as easy & 
transparent as a 'regular' update command (for which I rarely use the 
options dialog). This could probably be done using a macro, but I'd 
rather suggest using a separate 'native' command, since IMHO this is an 
option that is widely used, so it should get a prominent place next to 
the regular update command.
I even think this should become the default update mechanism when 
updating a sandbox that apparently was a virtual module checkout...

Comments?
</jum>

[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com.  Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/NhFolB/TM
---------------------------------------------------------------------~->

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/