Re: Suggestion for improved use of cvs checkout to update sandboxes

Jens,

> 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" 

I would say it's a good idea. In fact it's such a good idea that CVS 
should handle the whole thing so and the same should work from regular 
command line. One should be able to just do "cvs co" and CVS should 
use it's metadata to figure out the module and checkout as neccessary. 

Currently we have:

cvs co (in directory D:\CvsTest\loki)
cvs [checkout aborted]: must specify at least one module or directory

I think we could convince Tony to implement the caching of module in 
CVS metadata. Eventually we could have additional option for checkout 
command, like '-U', to make checkout read the modules and don't 
require explicitic module specification.

I think we should not have to store the module name - it's the CVS 
business to know what it's dealing with in the given sandbox. We 
should keep clear off storing any data in the sandboxes.

Best Regards,
Jerzy



------------------------ 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/