[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-06 14:42:55 CEST

kfogel@collab.net wrote:

> Ben Collins-Sussman <sussman@collab.net> writes:
>>This wouldn't be very hard to write. In the general case, we need some
>>sort of API for finding all revisions that contain a specific property
>>name/value. At the moment, this is already happening when we convert a
>>date to a revision. The RA->get_dated_revision() API scans all the
>>revisions, reading their 'svn:date" property and returns exactly one
>>revision. We just need to generalize this idea. It just that nobody's
>>bothered to do it yet.
> Er, that only scales because get_dated_revision can do a binary
> search, right?

isn't it easier if you just add a table and a pointer on each revision:

a table of [ revnum:number revnames:string ]
and each 'revision' gets an additional pointer/offset
into this table.

if you complete that with an additional path you
probably have a perfect description for a nonmodifyable "tag".
      [ revnum:number revnames:string subpath:string ]
e.g. [ revnum:16 revname:"myTag" subpath:"/trunk/project/calc" ]

and 'revision 16' points ( the same way it points to the
logmessage texts ) at this data field.
it's almost the same as adding a special comment to the
logmessage saying "{!!} Release 1.2 {!!}", but it would be
--standardized-- and (because of the small extra database table)
much faster than to search through all logs for this special marker.
ofcourse, currently eveybody can write that data down in his own
kind of 'Tags.README' and do log-searches, but no 'other' tool will
support that the same way. (sorry i'm repeating myself:)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 6 14:56:48 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.