| 1 |
On Tue, 12 Apr 2005 20:50:36 +0200 Paul de Vrieze <pauldv@g.o> |
| 2 |
wrote: |
| 3 |
| On Monday 11 April 2005 22:42, Ciaran McCreesh wrote: |
| 4 |
| > Well, surprisingly enough, one of the main reasons we use these |
| 5 |
| > version control things is so that we can see *what changed*. It's a |
| 6 |
| > hell of a lot easier to do this when you can just say "show me |
| 7 |
| > everything that changed in the foo project between three days ago |
| 8 |
| > and today" rather than having to worry about adding in extra |
| 9 |
| > selections to pick a project path. |
| 10 |
| |
| 11 |
| You need to do this anyway. Whether it's a path inside the repository |
| 12 |
| or on the webserver doesn't matter. It's like |
| 13 |
| https://svn.gentoo.org/gentoo/projA where /gentoo is the name of the |
| 14 |
| repos or https://svn.gentoo.org/gentoo/projA where /gentoo is a |
| 15 |
| superdirectory of all project repositories that are now housed in the |
| 16 |
| gentoo cvs repository. In either case /gentoo could be removed. |
| 17 |
|
| 18 |
No, with certain operations you need to start giving entire paths if and |
| 19 |
only if you're not operating on the repo as a whole. |
| 20 |
|
| 21 |
| > One big repository is harder to work with. It's that simple. |
| 22 |
| |
| 23 |
| With one exception, that is, sharing and merging within a repository |
| 24 |
| is a lot easier than between two separate repositories. |
| 25 |
|
| 26 |
Which is an extremely rare task compared to doing things like diffs and |
| 27 |
branch merges... |
| 28 |
|
| 29 |
-- |
| 30 |
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools) |
| 31 |
Mail : ciaranm at gentoo.org |
| 32 |
Web : http://dev.gentoo.org/~ciaranm |
Archives