Rob Carter wrote:
> Sorry, didn't realize you couldn't see the original post:
>
> > Scott Nicolson wrote:
> > > It would appear that viewing the log in a working copy of a project
does
> > > not parse the externals property (i.e. I would like to view the log
> > > history from the root of my project instead of having to view it
from
> > > each external directory separately). I guess this make sense when
> > > externals reside in different repositories but when they reside in
the
> > > same repository this would be something very nice to have (almost
> > > essential). Is there a configuration option for allowing this in
TSVN?
> > >
> > > Note this "show log" functionality is consistent with the "revision
> > > graph" functionality but inconsistent with the "show modifications"
> > > functionality. e.g. I right click on the project root, and select
'show
> > > log' and only see the log of the files within this project that
aren't
> > > brought in by the externals property. The same happens for showing
the
> > > 'revision graph', I only see the files contained within my project
and
> > > not for the externals. However if I right click on the project root
and
> > > select 'show modifications' the external directories are parsed
> > > correctly and I can see available updates for the entire project.
> > >
> To which Stefan responded:
> >
> > "Show log" (and the equivalent Subversion API svn_client_log()) only
> > shows the log of the path you specify, and all paths below that one.
> > You're externals are *above* that path, so the log isn't shown.
>
> So that all makes sense, except I don't get why "show log" behaves
differently
> from "show modifications" when used with externals. Is there some
inherent
> difference between the two commands that I don't understand? Or is this
a
> feature that could be implemented, it just hasn't been?
First of all, such feature would be at least somewhat useful -
even if the externals point to a other repositories. And it could
be implemented to be almost as fast as 'svn log -v'. There are
a number of pitfalls, though:
* what is the semantics for externals that have been fixed
to a specific revision?
* what is the semantics of "--limit" even for externals
pointing to HEAD in the same repository?
* the result could (probably) not be cached
If other externals to other repositories would be handled as well:
* how do I discern paths coming in from different repositories?
(log format needs to be extended)
* how do the revisions relate to each other (timestamps or revisions?)
Having said all of that, what is your concrete usage scenario -
for externals and how log should behave? There might be a way
to support a specific but sufficiently common use-case on the
client side with acceptable effort.
-- Stefan^2.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2576566
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-12 18:51:53 CEST