[PATCH] include limits.h instead of linux/limits.h for FreeBSD
jamie.couture at gmail.com
Sat Dec 17 13:31:44 CET 2011
On 12/17/2011 06:24 AM, Lukas Fleischer wrote:
> On Fri, Dec 16, 2011 at 09:01:23PM -0500, Jamie Couture wrote:
>> Likewise. I too can lend a hand applying / testing submissions.
>> I have done so already with a few that apply properly - some patches
>> need to be re-submitted.
>> I'm not sure if a fork is necessary yet; rather, someone Lars trusts
>> to pull changes from.
> So, that means that *you* will decide which patches are ready for
> mainline inclusion and Lars only merges your branch from time to time?
No, I'm not self serving - I wasn't referring to myself at all; it was
merely a suggestion.
> What's the difference to creating a fork then? Having one maintainer and
> several developers that the maintainer pulls from makes sense if there
> are loads of patches and/or different subsystems - it allows for sharing
> work efficiently. Or if there's a lot of patches that need to be rebased
> on each other and you want to assist with doing all the conflict
> resolution (which obviously isn't the case here).
> If you really want to help, what I'd suggest is:
> * Review and test patches. Reply to mails, give feedback and tell
> contributors if there's anything that should probably be fixed. The
> more people review, the better it helps Lars.
> * Try to contact Lars and ask him if there's anything else you can do to
> improve his response time. If he doesn't react for another 4 weeks or
> says that he won't be able to spend any time on developing cgit in the
> near future, we should find a new maintainer or start off a fork...
>> Also, tags haven't been signed since 0.8.1 (not sure if people care
>> about that one).
>> On 12/16/2011 08:17 PM, Norberto Lopes wrote:
>>> I actually have been applying the various patches in the one I build
>>> privately. It shouldn't be too hard to just commit them and have them
>>> available in github. I would rather not fork though as that would make
>>> one of us the decision makers for stuff that sometimes is not really
>>> easy to decide on (As an example, I just saw the discussion related to
>>> the ABI change for the nonset variable vs empty string). Instead I
>>> would gladly give a helping hand to Lars even though I am new around
>>> cgit mailing list
>>> cgit at hjemli.net
>> Jamie Couture
>> cgit mailing list
>> cgit at hjemli.net
> cgit mailing list
> cgit at hjemli.net
More information about the CGit