Re: OT: Version Control

This WebDNA talk-list message is from

2007


It keeps the original formatting.
numero = 69373
interpreted = N
texte = Nitai @ ComputerOil wrote: > You will want to have one repository for each project where each project has > a trunk, branches and tag directory. Only if you *never* intend to share code between projects. There are plenty of good reasons to have a single repository with multiple projects in it (each with their own trunk/branch/tag hierarchy). However, if you are doing projects for outside entities, it is just as useful to have separate repos for each project, and use svn:external links for shared library code (that way you can just archive and delete the projects you are no longer working on). Or, if your code is very modular, you could have a single repo for your common code base and separate repos for the site-specific pieces. TMTOWTDI... John ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: OT: Version Control ( John Peacock 2007)
  2. Re: OT: Version Control ( "Nitai @ ComputerOil" 2007)
  3. Re: OT: Version Control ( Clint Davis 2007)
  4. Re: OT: Version Control ( "Nitai @ ComputerOil" 2007)
  5. Re: OT: Version Control ( Clint Davis 2007)
  6. Re: OT: Version Control ( "Nitai @ ComputerOil" 2007)
  7. Re: OT: Version Control ( Clint Davis 2007)
  8. Re: OT: Version Control ( "Nitai @ ComputerOil" 2007)
  9. Re: OT: Version Control ( Clint Davis 2007)
  10. Re: OT: Version Control ( "Nitai @ ComputerOil" 2007)
  11. Re: OT: Version Control ( John Peacock 2007)
  12. Re: OT: Version Control ( Jesse Proudman 2007)
  13. Re: OT: Version Control ( Clint Davis 2007)
  14. Re: OT: Version Control ( Jesse Proudman 2007)
  15. Re: OT: Version Control ( Clint Davis 2007)
  16. Re: OT: Version Control ( Jesse Proudman 2007)
  17. OT: Version Control ( Clint Davis 2007)
Nitai @ ComputerOil wrote: > You will want to have one repository for each project where each project has > a trunk, branches and tag directory. Only if you *never* intend to share code between projects. There are plenty of good reasons to have a single repository with multiple projects in it (each with their own trunk/branch/tag hierarchy). However, if you are doing projects for outside entities, it is just as useful to have separate repos for each project, and use svn:external links for shared library code (that way you can just archive and delete the projects you are no longer working on). Or, if your code is very modular, you could have a single repo for your common code base and separate repos for the site-specific pieces. TMTOWTDI... John ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ John Peacock

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Getting real time CC's out of Australia (1998) [isfile] ? (1997) Item order (2002) [WebDNA] An unknown error occured // Deadlock avoided (2011) Can you do this??? and other stuff (1997) Need a little help with categories... (2003) Location of Browser Info.txt file (1997) Emailer setup (1997) Stopping bad HTML propagation ? (1997) Error Lob.db records error message not name (1997) Introduction/Tutorial/QuickStart (1997) rotating thumbnails (1997) Newbie Tax Question (1997) RE: type 2 errors with ssl server (1997) Multiple catalog databases and showcart (1997) the dreaded unitShipCost (2003) Two options to consider (2008) Attention all list readers (1997) template cache problem (1998) writefile - continued (1997)