Hi! Then you and others should stand up and provide feedback like this far, far earlier in the development process.
If everyone who communicates says "x" and no-one says anything about the other letters "a"->"w", "y", "z", then we as developers don't really have a good cross-section of what people actually need. If you truely are doing things that require this level of service(s), then I encourage you to contact the FreeBSD Foundation and communicate exactly what your requirements are and why. They'll be able to steer things. Thanks! -adrian On 7 October 2013 16:00, Lyndon Nerenberg <lyn...@orthanc.ca> wrote: > > On 2013-10-07, at 3:45 PM, Lyndon Nerenberg <lyn...@orthanc.ca> wrote: > > > Having RCS in the base system is very useful. We use it to track > changes to bits of /etc on the machines where we don't do wholesale > customizations. (Those ones get git, but they also get an install of > /usr/ports with a fully populated /usr/ports/distfiles.) > > To clarify, the git-enabled machines are a small isolated subset of the > development machines. Then comes the test and q/a environment, where we > (by contract) roll nothing beyond the base OS and our application software. > > There are other development shops dealing with the same restrictions. > Most of them have to stay quiet about these requirements on account of the > Homeland Security. They are all getting buggered over by the fallacy that > everyone has a gigabit ethernet connection permanently wired into their ass > ... > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
