On 05/01/2014 11:01 PM, Jiri Svoboda wrote: > Is there any practical reason why it needs to be in a separate source > code repository? Why can't it be in the mainline repository?
Perhaps not a practical reason, but it helps to keep the mainline clean of any ported code. Making the HelenOS code a first-class citizen, a distinction between ours and theirs. We can enforce different standards on the two bases (cstyles, optimization options, warning levels, licesnes). On the other hand, it would be practical, to have coastline matrix rebuilt every time there is a push to mainline, to see whether somthing broke. Finally, should not be libposix moved to coastline as well? It has only a very limited reason to exist without it. Jakub > > -Jiri > > ---------- Původní zpráva ---------- > Od: Martin Decky <[email protected]> > Komu: HelenOS development mailing list <[email protected]> > Datum: 30. 4. 2014 0:03:24 > Předmět: [HelenOS-devel] Coastline turning official? > > > Hi folks, > > > I would like to move pcc from mainline to coastline. The first step is > > providing a harbour. Vojta, can you please review and consider the > > attached harbour for inclusion in coastline? > > As we are moving stuff from the mainline to the coastline, I suggest we > finally adopt the HelenOS Coastline as an official project. Therefore I > have created a repository for it: > > bzr://bzr.helenos.org/coastline > bzr+http://bzr.helenos.org/coastline > > I believe Vojta should have the privilege to import the contents of his > git branch into it. > > > M.D. > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > > > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
