Mark Phippard wrote:
>> I also would like to look at support for common History view
>> introduced in Eclipse 3.2. Is this branch would be the right place to
>> work on such patches?
> Unless there was something about Brock's changes that were needed for this
> change, it'd be better to just make the patch against trunk. I could then
> commit it to a feature-branch until we decide what we are going to do with
> our releases.
> I saw you entered an issue, go ahead and attach patches to it when you
> have them.
That is what I entered issue for. :-)
> I am just curious what the goals/benefits will be of making
> this change?
I keep history view on my Java perspective stacked with other views
such as Console, Search, etc. to have it handy. Because I have projects
from both CVS and SVN repositories currently I ended up with 3 history
views (cvs, subclipse and subversive) and they clutter the UI. So, it
would help if I can eliminate at least Subclipse's proprietory history
view and reuse common History view.
> Also, in making it we would have to not lose any features of
> the current view. The main ones I mean would be things like support for
> the --stop-on-copy option, the use of the --limit option to only fetch
> history N revisions at a time, issue tracking integration, being able to
> show tags via the subclipse:tags property etc. I am fine with someone
> adding this, but I'd like to know what the perceived benefits are going to
> be so I know how to evaluate the patch.
I agree and don't want those troubles either. So, the plan is to add
custom page to History view, but content of that page and most of the
implementation would be exactly the same as current Subclipse history view.
Received on Sun May 21 21:01:32 2006