Re: Keeping tags/ and branches/ in the trunk
Greetings, trans! Is it possible to keep tags/ and branches/ in the trunk/ so as not to have to differentiate these three at the top of a repository. Everything is possible, but ask yourself, do you really want to checkout whole repository every time you request to checkout trunk? In other words, instead of: branches/ BRANCH_xyz/ tags/ RELEASE_1_0_0/ trunk/ README bin/ lib/ One could have: README bin/ branches/ BRANCH_xyz/ lib/ tags/ RELEASE_1_0_0/ I think I might prefer this approach, if possible. The problem of course is in creating new tags and branches, i.e. making a copy, I would need to prevent the tags/ and branches/ directories from being copied in the process. Is there a way to do that? And this one, too. Read svnbook... SVN is a filesystem, all basic rules of file handling apply. -- WBR, Andrey Repin (anrdae...@freemail.ru) 25.01.2010, 17:45 Sorry for my terrible english...
Re: Keeping tags/ and branches/ in the trunk
On Jan 25, 9:30 am, Andy Levy andy.l...@gmail.com wrote: I don't understand what advantage this would give you. I do see the potential for a lot of confusion and copying/moving of items which shouldn't be operated on, though. Subversion itself applies no special meaning to tags branches so there is nothing *technical* from stopping you from doing this; it seems like you're going against convention for no discernible reason though. Merely convenience --perhaps a minor reason, but a reason nonetheless. At least for me, I find it nice to have the source code closer to the surface. Having now used git for some projects its one of the things I find I like about it. However I prefer Subversion's approach to tags and branches. So I simply wondered, would it be possible to have both? But there are problems with the approach, e.g. checking out the trunk would pull down the tags and branches as well. So I am inquiring if there is anyway to configure Subversion to exclude paths from a checkout, as well as tagging, branching, etc. that would make this doable. trans
Re: Keeping tags/ and branches/ in the trunk
On Mon, Jan 25, 2010 at 11:05, trans transf...@gmail.com wrote: On Jan 25, 9:30 am, Andy Levy andy.l...@gmail.com wrote: I don't understand what advantage this would give you. I do see the potential for a lot of confusion and copying/moving of items which shouldn't be operated on, though. Subversion itself applies no special meaning to tags branches so there is nothing *technical* from stopping you from doing this; it seems like you're going against convention for no discernible reason though. Merely convenience --perhaps a minor reason, but a reason nonetheless. At least for me, I find it nice to have the source code closer to the surface. Having now used git for some projects its one of the things I find I like about it. However I prefer Subversion's approach to tags and branches. So I simply wondered, would it be possible to have both? But there are problems with the approach, e.g. checking out the trunk would pull down the tags and branches as well. So I am inquiring if there is anyway to configure Subversion to exclude paths from a checkout, as well as tagging, branching, etc. that would make this doable. Sparse Checkouts will handle the former, but the latter you'll have to step very carefully or script your branching tagging (and may have to do it in steps, instead of all at once).
