Attila Tajti wrote:
> Finally some feedback. :) Thanks again for looking at this.
> I think properties would be surely better. At least we wouldn't need
> another set of options in TSVN settings for that. :) But I'm more
> concerned about the implementation right now.
We discussed this kind of properties some time ago. We could use them
for other features too. So yes, I'm in favour of properties too.
> First I think this feature should be implemented on the server side but as
> far as I know this can't happen until after Subversion uses a relational
> database backend, so implementing it on the client side support is the
> second best option.
This has nothing to do with the db backend. It has to do how revisions
are stored in the currently used backend. It only stores immediate
copies. So for example, if you create a copy (tag) from trunk@100, you
don't get that information by showing the log of /trunk/file. Because
the copy information is only stored for "trunk", not its children.
That's also the reason why the revision graph has to fetch the log from
the repository root - we couldn't get the information when e.g. a tag is
created from a branch because we don't get that information by showing
the log of trunk.
> If I understand Stefan correctly for generating this kind of log (or a
> revision graph) the client has to get the log for everything from the
> repository root. When I first looked as Work Bench I thought it cached
> this info, ie. it fetched everything related to tags and branches and
> saved it locally so it doesn't have to fetch everything all time. At
> least notes/schema-tradeoffs.txt suggested it was possible.
> Isn't that be possible? Once we have this cache we could update it
> from the newest known revision.
See issue #45:
But I know this would be a nice feature. I have to study the subversion
code a little bit more. Maybe I can find an easier way to accomplish
that, but maybe it's just not possible without showing log for
repository root - we'll see...
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Oct 4 20:33:06 2005