Eugene Kuleshov <firstname.lastname@example.org> wrote on 06/19/2005 10:03:49 PM:
> >> Is there are anything else todo around resource histories?
> > I would like to see it enhanced to use the new --limit feature of
> > With this, we could just ask the server for the last N log messages.
> > then add some kind of support for getting the next N as needed. This
> > perform better, especially when 1.2.1 is released.
> Does this require support from server or just new client?
The Subversion support is there, we would need to add new methods to
ISVNClientAdapter as well as implementations for JavaHL and the CLI. I
only mentioned 1.2.1 because there is a performance problems with this
feature in 1.2.0.
> > I would like to see searching/filtering of log messages added.
> I'm not sure how filtering could look like, but I can take a look on
I was thinking two things for filtering.
1) Say you have a bunch of revisions loaded. A search option could
search the data that is loaded, and filter the view to only show the
2) Some new options on the view to grab a specific set of messages, such
as between dates X and Y.
An idea might be to change the Show in Resource History action to first
display a dialog that lets the user indicate how many messages to fetch
and/or a date range for the messages. Just thinking out loud.
> > Perhaps more compare options or other features such as initiating a
> > merge to back out a revision.
> I was looking trough comparison yesterday, and wasn't able to find
> much, except features like "Compare with revision..." or "Compare with
> tag/branch..." that allows to choose second file to compare. There could
> be some cosmetic changes, like show compared revisions/branches in
> comparison editor.
> I have to admit that I don't feel ready yet to work on things like
I was mainly thinking about:
a) make compare enabled in more circumnstances. Currently, you can only
do compare if you are showing the revisions for a specific file.
b) perhaps provide a few compare options. Such as showing the specific
change for that revision (probably in diff format). Comparing against the
local pristine copy vs. the local edited copy. Perhaps options to show
unified diff of the entire revision? Like a patch option?
> >>>Of course you also should set your root, but this sort of code should
> >>>there as a fall back.
> By the way, current repository properies dialod doesn't allow to see
> URL if label had been changes. I add some static non editable label that
> will show this URL to this dialog. What do you think?
I think that is a good idea. Please send a patch.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Tue Jun 21 00:35:51 2005