[egit-dev] SWT thread access error, but it was just me

[denstar <valliantster@xxxxxxxxx>]

I was getting an invalid SWT thread access error after committing anything.

I assume it's only because of what I'm rocking locally for the key
bindings, and y'all don't have to worry about it.

I'm just posting this because last time I made that assumption, it
wasn't the case.

Others would for sure be seeing this one tho, so I'm pretty sure this
time it's just me.  :)

Fixed easily enough.  Still loving my ugly patch.  :-)

I just verified that there are no null pointers with the latest
untainted-by-I source, so never mind, it was just me.

Is it worth it to anybody for me to continue perusing this within the
EGit system?  I seems like it's only useful to me, and other folk
either aren't all into keybindings, or are getting by with what's
there.

I tried using what was there myself, but intermittently getting the
wrong selection was driving me nuts.

Maybe that fixed itself now though?  I guess I could test that theory
myself easily enough :)  Haven't seen anything go in that would have
changed the behavior though, I don't think.

Anyways, whatever I did with gerrit is just sorta hanging there...
does someone want to be a reviewer or should we just table this stuff?
 I'm already forgetting what I learned for gerrit, and with all
honesty I'm not lamenting it too much.  :)

gerrit: http://egit.eclipse.org/r/#change,376
(useless now, but I've been keeping it up locally)

Here's the old bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=290637

That's that, I reckon.

In closing: y'all are doing a fabulous job!  Keep it up!

And feel free to not even think about this stuff-- compared to what's
on The List, it's not urgent in the least.  Just figured I'd send this
out and touch base sorta, for kicks, and to at least mention that you
guys are moving along at a good clip, which is swell, just swell.
Props, so to speak!

:Den

-- 
Face the facts of being what you are, for that is what changes what you are.
Soren Kierkegaard