[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH] ksysguard lm-sensors fix
From:       Alexey Chernov <4ernov () gmail ! com>
Date:       2011-02-05 12:21:13
Message-ID: 201102051521.13300.4ernov () gmail ! com
[Download RAW message or body]

On Saturday 05 February 2011 03:42:25 Aaron J. Seigo wrote:
> On Friday, February 4, 2011, you wrote:
> > > On Thursday, February 3, 2011, 4ernov wrote:
> > > > I've fixed a bug in lm-sensors' part of ksysguard which concerns its
> > > > work with multiprocessor systems. The bug is discussed in this
> > > > report: https://bugs.kde.org/show_bug.cgi?id=251145 - Sensors tab
> > > > and Sensors plasmoid don't see more than 4 cores with 2.6.35 kernels
> > > 
> > > i've reviwed all 4 of your patches and merged them. thanks!
> > > 
> > > if you'd like to continue fixing bugs and improving the code, you
> > > should really consider getting a commit account of your own :)
> > 
> > Aaron, thank a lot for reviewing and merging my patches, my very first
> > patches to KDE, it was really brilliant news last morning :) Yes, I
> > hope to continue fixing some bugs, also have some plans. But is it
> > really possible to have such an account for this?
> 
> yes, of course! you can still get patches reviewed as you need or if your
> changes are on other people's code, but you can at least then push them
> yourself when they are ready (which could be instantly if they are
> "obvious" fixes).
> 
> my suggestion is this: make yourself an account on identity.kde.org, then
> when you next have a patch ready to push apply for a commit account, also
> via identity.kde.org, and you can put me down as your reference.
> 
> welcome to KDE! :)

Thank you very much! And also thanks for detailed instructions. So I know what 
to do when my next patch is done :)
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]