[news.eclipse.platform] Re: can I remove a workspace from the "switch to

[Eric Rizzo <eclipse-news@xxxxxxxxxxxx>]

On 2/17/2009 1:44 PM, Paul E. Keyser wrote:
> Eric Rizzo wrote:
> > On 2/6/2009 10:43 AM, Paul E. Keyser wrote:
> > > Eric Rizzo wrote:
>
> > > I notice that there is also a pref. "MAX_RECENT_WORKSPACES=5" from which
> > > I found the relevant feature-request:
> > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=162102
> >
> > A bug report that old with no activity is unlikely to get addressed
> > without some contribution from the community. This seems like a
> > reasonable thing for someone to provide a patch for. Care to take it on?
>
> Eric --
>
> Thanks, I might well be interested in doing that. However, I seem to
> have at least two problems: (a) it takes me a while to get around to
> this sort of thing (b/c I have too much to do already), as in:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=151469

In that case it looks like what you submitted could not be easily 
digested; they really need patches as opposed to stand-alone code. It 
looks to me like the last bit of info came from Paul instructing you how 
to get the Eclipse code from CVS, which would enable you to create a 
patch pretty easily.
That is a pretty old bug against 3.1, so I'm not sure it is still 
applicable; but I'd encourage you to pick it up again. I'd say you're 
only a couple of hours of work away, assuming the code in question 
hasn't changed too much since 3.1.


-- and (b) even
> when I do get around to it, somehow, the system stalls after I have
> submitted, as in https://bugs.eclipse.org/bugs/show_bug.cgi?id=104561 --
> is there something else I am doing wrongly (besides being durn slow)?

In that case I'd ping the bug with a comment, since it appears that you 
were actively addressing the feedback but it stalled. A comment will 
trigger an email to all the CCers, most importantly Dale and Wayne.

Eric