Qtopia: 391

Allan Clark allanc at chickenandporn.com
Wed Sep 7 07:57:07 UTC 2005


Hi Everyone;

This is a (buildroot) thread that was first ignored 18 days ago, more or 
less.

Who can I send beer to to either:
1) test this patch in their systems?
2) check this patch into SVN?
3) let me check the patch into SVN, and any other patches that are there?

There are a number of feature requests for buildroot that are simply 
sitting untouched in thre bug reporting tool.  Implicitly, feature 
requests that include patches should be implemented rather quickly, but 
that's not happening (granted, 18 days is not a huge time, but it is if 
I've made changes, and now much implement a CVS over my SVN repository 
to track my changes that are not yet in SVN... ridiculous?)

How can I get my patches in?  How can I get others' patches in?

I'm willing to patch-monkey for a while:
  if exists patch-file
    if cleanly patches my directory
      if builds without breaking
      then
      {
        apply patch to svn
        mark bug to some kinda testing mode
        get confirmation from author
        close bug
      }

It would be nice to use some of this submitted stuff.

Who do I need to send beers to?

Allan
--
As an aside, paypal needs a beerpal alternative.


Allan Clark wrote:

> Hi Mike;
>
> Is this something I can just check in myself to SVN?
>
> Allan
>
>
> Allan Clark wrote:
>
>> Hi Mike;
>>
>> I'm not sure who to ask... I want to rush patch#391 into buildroot.
>>
>> I've added a patch for Qtopia to buildroot, I want to begin extending 
>> it and testing it on other releases.  I want to augment what is 
>> there, but I don't want to pollute my original patch in my area in 
>> case I need to edit it for when it's finally added.
>>
>> Can I do the checkin myself, do I need additional access, what is my 
>> next step?
>>
>> Allan
>> -- 
>> MSN is email addr ; skype: chickenandporn ; talk.google is 
>> chickenandporn
>
>




More information about the uClibc mailing list