Think it might be useful to, like, pin this to an OSI layer? You're going to be including all sorts of ludicrous stuff, like gcc & svn/git.
Critical internet software, that's the stuff that makes happy machines speak transport layer to each other. That list is already huge without including every httpd and library in the universe, every compiler and flavor of Unix. Travis On Aug 3, 2014 10:50 AM, "Bill Woodcock" <[email protected]> wrote: > > Without making any claims as to the value of maintaining such a list, I'll > point out that I included gcc. > > -Bill > > > > On Aug 3, 2014, at 3:06, "danimoth" <[email protected]> wrote: > > > >> On 02/08/14 at 07:36am, Rich Kulawiec wrote: > >> I think this list is a pretty good starting point. Of course, > >> having said that, now I want to edit it. ;) > > > > IMHO the idea is pretty stupid. The "implementation" also, because > > nobody mentioned a compiler.. lol, how to waste time > > -- > > Liberationtech is public & archives are searchable on Google. Violations > of list guidelines will get you moderated: > https://mailman.stanford.edu/mailman/listinfo/liberationtech. > Unsubscribe, change to digest, or change password by emailing moderator at > [email protected]. > > > > -- > Liberationtech is public & archives are searchable on Google. Violations > of list guidelines will get you moderated: > https://mailman.stanford.edu/mailman/listinfo/liberationtech. > Unsubscribe, change to digest, or change password by emailing moderator at > [email protected]. > >
-- Liberationtech is public & archives are searchable on Google. Violations of list guidelines will get you moderated: https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe, change to digest, or change password by emailing moderator at [email protected].
