← Back to team overview

coapp-developers team mailing list archive

Thread
Date

Re: I think we'll want to fork gnulib

To: Garrett Serack <garretts@xxxxxxxxxxxxx>
From: Adam Baxter <voltagex@xxxxxxxxxxxx>
Date: Wed, 28 Sep 2011 17:55:32 +1000
Cc: "coapp-developers@xxxxxxxxxxxxxxxxxxx" <coapp-developers@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <1B45B1F7406FEA4C937840018B0C9E050A093224@TK5EX14MBXC284.redmond.corp.microsoft.com>

Do you end up with an #ifdef soup with this approach?

The two things that spring to mind here:
* Library A needs work to make it good for us. Library A is then updated -
what work do we need to do keep pace with mainline?

* Do we try to get Windows specific patches integrated back upstream at any
time?

Follow ups

Re: I think we'll want to fork gnulib
From: Ted Bullock, 2011-09-28

References

I think we'll want to fork gnulib
From: Vincent Povirk, 2011-09-24
Re: I think we'll want to fork gnulib
From: Adam Baxter, 2011-09-25
Re: I think we'll want to fork gnulib
From: Vincent Povirk, 2011-09-25
Re: I think we'll want to fork gnulib
From: Adam Baxter, 2011-09-26
Re: I think we'll want to fork gnulib
From: Garrett Serack, 2011-09-27