Based on your explanation on how "show log" works, would the following idea be feasible?
The log for e.g. /trunk shows those revisions that have changes to and below /trunk. For every of those revision, if there is an externals property which refers to the same repo, then add all revisions that have changes to and below the externals path but only if a revision is not already included because of changes in /trunk (i.e. eliminate duplicates). In other words: The "show log" command builds an initial list of revisions based on the primary path, then follows all externals it can find in that list and adds any revision with changes in an external path if the given revision is not already present in the list. Udo On Sunday, February 2, 2020 at 7:33:47 PM UTC+1, Udo Eberhardt wrote: > > Hmm. You are right, that's a problem. However, to me it would make sense > if the log considers the externals which are present in the latest > revision, or alternatively in the working copy. > > I find the current behavior confusing because my project tree includes > several external libraries and it is difficult to get an overview of all > changes. > > > On Sunday, February 2, 2020 at 3:44:49 PM UTC+1, Stefan wrote: > >> What your asking for is not really feasible. Think about it: >> when you do a commit, the external properties are right there in the >> working copy. So a commit has that information ready. >> But to show a log, that information is not readily available: the >> external properties can change in any revision. >> > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/4a003dc3-6090-4021-b40e-a51b5f1c1c65%40googlegroups.com.
