[Buildroot] commiting patches

[Heiko Zuerker]

Quoting Peter Korsgaard <jacmet at uclibc.org>:

>>>>>> "Thomas" == Thomas Petazzoni  
>>>>>> <thomas.petazzoni at free-electrons.com> writes:
>
>  Thomas> Hello,
>  Thomas> As this is my first message to the list in 2011: happy new year
>  Thomas> everybody. Best wishes for 2011, and let's have some good BR
>  Thomas> development during this year :-)
>
> Yeah!

Happy New Year to everyone too.

>  >> I mainly try to handle the patches in fifo mode, but I do also skim
>  >> new mails. This is both because sometimes updates are sent, and
>  >> sometimes I see trivial patches that can be handled when I have 5
>  >> min spare or important bugfixes.
>
>  Thomas> I think there is also one criteria that has an impact of the
>  Thomas> time it takes for a patch to be applied: what the patch
>  Thomas> does. If the patch is a relatively simple fix to a package, a
>  Thomas> new package, or something that doesn't have any major impact of
>  Thomas> Buildroot's infrastructure, or Buildroot usage, then this patch
>  Thomas> is likely to be handled/merged sooner than something that has
>  Thomas> broader impact.
>
> Indeed, that's what I meant when I wrote about trivial patches.

Makes perfect sense.
I also understand that I'm new to BR and still have a lot to figure out.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.