On Mon Dec 27 10, Ade Lovett wrote:
On Dec 26, 2010, at 15:00 , Alexander Best wrote:
it seems this issue is one of the cases where everybody is too afraid to
make
the actual commit. :(
More likely, it's a case of let's get 7.4/8.2 out the door, with the usual
rush of MFCs.
I have a feeling that 9.0 (perhaps the entire 9.x tree) is going to be pretty
brutal. Whether it's with gcc and clang side by side, or just clang. A
change of this magnitude is going to _hurt_.
if i understood the previous comments correctly this change will have *no*
impact whatsoever appart from keeping stdout/stderr a bit cleaner.
well...of course rushing changes is not a good idea but the opposide is just as
bad. there are hundreds of very techie discussions where developers aggree on a
certain item, but after the discussions ends nothing happens.
e.g.:
- switching the source for pciconf
- mfc'ing the latest awk release to stable/7
- fixing some serious data corruption in the mailinglist archives
- revising BDECFLAGS
- ... plus numerous PRs which contain *correct* patches, now outdated due to
their age.
also this is very discouraging. a lot of people stop their community support,
since their work (e.g. patches) dye of old age in some problem report.
personally i write far less patches than i used too, simply because most of the
time nobody will help you get the patches committed, even if they fix trivial
spelling mistakes in manual pages.
just my 0.02$.
cheers.
alex
-aDe
--
a13x
___
freebsd-toolchain@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to freebsd-toolchain-unsubscr...@freebsd.org
