Date: Thu, 24 Jun 2010 21:37:35 +0200 From: Alexander Best <alexbestms@uni-muenster.de> To: utisoft@gmail.com Cc: freebsd-questions@freebsd.org Subject: Re: sharing code between the various *BSDs Message-ID: <AANLkTinxS4d0Ku65a1E8nIAHJJaR0Dj0M1_ihZioKwS7@mail.gmail.com> In-Reply-To: <AANLkTik4noWKbphaQ3VADO1Vt0JJxtJimN25gFbcHVKl@mail.gmail.com> References: <AANLkTikCxIsbWKbWVPlkHnzsfhCtYiX2kX4iVz_pcC12@mail.gmail.com> <AANLkTik4noWKbphaQ3VADO1Vt0JJxtJimN25gFbcHVKl@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 22, 2010 at 12:13 AM, Chris Rees <utisoft@gmail.com> wrote: > Politics... too bad politics get in the way of progress. :( > > Sorry for top-posting, Android won't let me quote. There's a bug report on > it! > > On 21 Jun 2010 23:12, "Alexander Best" <alexbestms@uni-muenster.de> wrote: > > hi there, > > i can't remember where i read this the other day, but i found this to > be a great idea. basically the idea was to have one code pool which > all the *bsd flavours share and also to which every *bsd committer has > access and can make changes. especially code in /bin, /sbin, usr/bin, > /usr/sbin or /usr/share (probably other places too) would benefit from > this a lot. right now most of the work that gets done in one of these > places by lets say dragonfly won't make it into freebsd or netbsd for > a long time. or what's even worse: sometimes people document problems > or bugs which have already been fixed in some other *bsd. if somebody > fixes the problem that's just wasted time because it's been done > beforehand. > > would this be even possible or not at all? > > -- > Alexander Best > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- Alexander Best
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinxS4d0Ku65a1E8nIAHJJaR0Dj0M1_ihZioKwS7>