> > The requested feature does not need any information about the link between source and target of a tag. To clarify the proposition the following example of desired log window could be presented:
> > Log Messages - .../trunk/Component
> > Revision|Message |
> > 12 |Version 1.0.2 | -- from log of /tag
> > 10 |serious bug fixed|
> > 5 |added a function |
> > 3 |Version 1.0.1 | -- from log of /tag
> > 2 |light refactoring|
> > - While the log of /tag contains only two lines.
> > - Is the idea more clear now?
> Not really. There could be hundreds of items within /tags. How do you
> know which ones are related?
> Assuming you have some way of doing that, then you are asking to get
> the log for the main requested item AND the log from tags and
> interleave the two. Is that correct?
-- Yes, it is mainly correct - you should interleave the two logs. But you have not to get only related items - result log contains all items from two logs.
And, as already mentioned, additional (second) item to get log from could be set not to "tags", but for example to some file "trunk/Version/version.ini", which is changed by build system.
Whether to output additional item log that could be set by a checkbox in log window.
And, as a light improvement, while outputing additional item log, by another checkbox value you could omit all lines but first from a dense set of log lines.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-17 13:06:20 CET