[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Roadmap for 1.1

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-04-05 19:22:08 CEST

>> > just keep a table in a file somewhere known in the repository.
>> this will limit you to use one single tool to work with the
>> repository, because each tool would have its own implementation of
>> 'named tags' and be incompatible to other tools. there must (should)
>> be a common design for this. I have created my own 'hack' for named
>> tags to fit my needs meantime, but I'm unhappy with it because no
>> other tools will ever go and support them.

Jeremy Pereira wrote:
> Which is one reason why it might not be a good idea. Another one is
hat does 'it' refert to here?

> that it is sort of against the conceptual model of Subversion (revision
> aliases are simple to implement so there is probably a philosophical
> reason why the developers haven't implemented them).

the revision aliases are great. i use them 95% of the time.
but 5% of the time i have to ask
"in which releases was this buggy 'file.c' included?"
and want a FAST answer to that, not wading through 26237 log messages
resulting in some 6 mb transferred over my 10kB/s line
or through 1756 "tag" and "branches" folders in 3 different repositories.
when its so easy to lookup the list of tags recorded in a single "Tags"
file that even gets automatically updated/patched on every 'tag' action
by just adding a few bytes. i really like my little buggy ruby --tag
script :)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 5 19:23:04 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.