Michael Haggerty wrote:
> Karl Fogel wrote:
>
>> Steinar Bang <sb_at_dod.no> writes:
>>
>>> But one thing I've never understood, is why they are "branches by
>>> convention". You guys have a very flexible metadata system, no? So why
>>> not put a property on the top dir of a branch or a tag, saying that's
>>> what it is?
>>>
>> We might someday, but we weren't sure (right now) what we'd do with
>> that. One of the nice things about a flexible metadata scheme is that
>> you don't have to design all your features at once :-).
>>
>
> I've thought that it would make sense to add a property to the trunk
> directory that indicates "this is a project root directory" (in the
> sense that it is the root of a source code tree, typically the level
> that users check out). The property would help scripts orient
> themselves. Moreover, it would automatically get propagated when trunk
> is copied to make a tag or branch, making it obvious (with no more work)
> that *those* are also project root directories.
>
> The point of such a property would mostly be to serve as a line of
> demarcation between the project/trunk/tags/branches namespace
> interesting in the SCM world and the filename namespace interesting for
> working copies, build tools, etc.
>
> If there were a standard convention and name for such a property, then
> tool builders might start using it.
>
Reading this and similar proposals makes me want to cry. People keep
proposing hacks upon hacks upon hacks instead of recognizing the
fundamental truth that our branching model is broken.
Deal with it. I've had my catharsis and am all better now, no more
jitters and insomnia. Highly recommended.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-19 10:53:17 CET