trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: November 2011

Re: [trinity-devel] Appeal for freedom of speech

From: "Timothy Pearson" <kb9vqf@...>
Date: Sat, 12 Nov 2011 14:55:46 -0600
> On Sunday 13 November 2011 00:29:39 Timothy Pearson wrote:
>
>
>> The only submitted patch
>
> This is not true. I contributed these patches:
> http://www.trinitydesktop.org/patches/1317502993:5402bbfde73f33c76f17a72bcd6ea3d730681fb9.diff
> http://www.trinitydesktop.org/patches/1315109543:90c6afc471fdb1a7761a1fab5094a25299018ec1.diff
> http://www.trinitydesktop.org/patches/1304806557:e789477ef1d0a99f7795890210b4fb68f45fffdc.diff
> http://www.trinitydesktop.org/patches/1299984139:790391e3a90a709160301953e47bd8f2fdc39c07.diff
> http://www.trinitydesktop.org/patches/1298313909:f0023a8307d74fa725424821433582eea645a4c5.diff
> http://www.trinitydesktop.org/patches/1297797316:cc0ad49c75d6cf6b4e63eb8c6012afe55c1589f9.diff
>
> and a fix to this bug:
> http://bugs.pearsoncomputing.net/show_bug.cgi?id=139

Good catch--I was looking only at Patchwork which did not show those
patches.  However, bear in mind that I tend to batch commit, so the
patches referenced above *contain* your patches but also may contain
TDE-originated patches and are therefore may not be completely yours. ;-)

>
>> (http://patchwork.trinitydesktop.org/project/trinity/list/) removed a
>> large chunk of HAL-dependent functionality and was therefore not
>> included.
>
> As can be seen from the patch, it does not remove any functionality, just
> the opposite, it enables and repairs
> a large part of code previously commented out and repairs other minor
> issues.

It forces the usage of a "/media" directory, which could lock TDE to a
specific set of distributions.  I have not given that patch a closer look
because of this potential issue.

There was another HAL "fix" patch that was rejected that did disable a
large chunk of the automounter functionality (the popup itself IIRC)--this
is what I was referring to earlier.

Are you planning to rewrite knetworkmanager in your repository to work
with the new NM 0.9 API?  NM 0.8 and below (and the associated APIs) are
obsolete now, and a native network manager applet is an often requested
feature.

Tim