I've now completely implemented this, as well as enabling arbitrary battery
and volume level enums (and various other WPS features fixes) - it's
exactly right.
Patch demo WPS here: http://www.rockbox.org/bugs/task/4802
Note that there's a change from my previous example; there is no step
On 3/8/06, gl [EMAIL PROTECTED] wrote:
After Linus was about to commit one of my patches, it turns out the project
leaders are not willing to accept contributions under a pseudonym. This may
be normal in the GPL world, but for someone from the Windows / BSD license
world, this seems utterly
here we go again...
gl wrote:
After Linus was about to commit one of my patches, it turns out the
project leaders are not willing to accept contributions under a
pseudonym. This may be normal in the GPL world, but for someone from
the Windows / BSD license world, this seems utterly
On Wed, 8 Mar 2006, gl wrote:
After Linus was about to commit one of my patches, it turns out the project
leaders are not willing to accept contributions under a pseudonym. This may
be normal in the GPL world, but for someone from the Windows / BSD license
world, this seems utterly bizarre.
Hi,
Neon John wrote:
Even though I use my real name in places like this I don't think I'd want it
plastered all over the net in software.
Maybe I don't understand the privacy in software madness, but your
name has been recorded all over the rockbox mailinglist archives. Those
archives are
On Wed, 2006-03-08 at 13:33 -0500, Neon John wrote:
Unfortunately you're not the first developer run off by this petty
power ploy. I certainly hate to see it but there is little I can do
as a user other than express my displeasure.
If you care about this issue so strongly, I think the most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
gl wrote:
After Linus was about to commit one of my patches, it turns out the
project leaders are not willing to accept contributions under a
pseudonym. This may be normal in the GPL world, but for someone from
the Windows / BSD license world,
sigh
What a shame.
Guys, what about this In reflection we cannot afford to lose good
coders. The problems between us and BC run deeper than anything that
was published online. Let's face it, we simply clash at some
undefinable core level. The rule put in place at the moment of that
crash
