Date: Mon, 11 Jun 2001 18:56:00 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: "Andrey A. Chernov" <ache@nagual.pp.ru>, "Bruce A. Mah" <bmah@FreeBSD.ORG> Cc: Nik Clayton <nik@FreeBSD.ORG>, current@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: HEADS UP: doc/ tree frozen (was Re: HEADS UP for /usr/src/release/doc & /usr/doc) Message-ID: <p05100e1fb74aef68c95b@[128.113.24.47]> In-Reply-To: <20010612011807.A49698@nagual.pp.ru> References: <20010611161221.C34164@nagual.pp.ru> <200106111337.f5BDbCE30451@sakura.mk.bsdclub.org> <20010611175041.A35687@nagual.pp.ru> <200106111551.f5BFpWE30649@sakura.mk.bsdclub.org> <20010611201531.A38114@nagual.pp.ru> <200106111645.f5BGjNA08546@bmah-freebsd-0.cisco.com> <20010611211953.A39062@nagual.pp.ru> <200106111842.f5BIgRB13547@bmah-freebsd-0.cisco.com> <20010611230213.A47504@nagual.pp.ru> <200106112035.f5BKZdU17583@bmah-freebsd-0.cisco.com> <20010612011807.A49698@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:18 AM +0400 6/12/01, Andrey A. Chernov wrote: >I understand now. That info you can provide from the beginning >to minimize messages exchange. I am open to discuss how to fix it. I think it is probably best to let Bruce Mah figure out why it has broken, and let him provide the best "immediate fix" for that problem. This is not a good time to start on some larger debate. Just let them fix it. >My suggestions are: > [...] >or > Backing out my doc/ changes. > (YES!!! I realy tired of amount of complaints given on > this technically simple issue from doc/ people. Nobody > can be 100% accurate. People are probably particularly sensitive to this change because it broke freebsd-stable. I realize you were not expecting any affect at all in freebsd-stable, but this area of the system is apparently set up in a way where it is not easy to make changes to "just freebsd-current" without some side-effects for freebsd- stable. Even if the change you MEANT to make is "technically simple", it is just a major hassle if freebsd-stable is broken. The fact that you didn't MEAN to break stable does not actually help anyone. As long as stable remains broken, then they still can not get on with their own work, and they will still be upset with you. It is not that everyone hates the specific change you were making, it is that everyone hates it when freebsd-stable can not be built. (SOME people may not like the specific change, but EVERYONE hates it when freebsd-stable is busted...) It also did not calm people down when you did not understand that they were complaining about freebsd-stable. The more you replied about freebsd-current, the more anxious and upset everyone will become. My hope is that Bruce (or Nik, or someone...) can also come up with a longer-term fix such that changes to RELNOTESng on freebsd-current will not break system builds on freebsd-stable. Since I am pretty useless when it comes to documentation (I am a systems-programmer after all :-), I'll let them worry about the details. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05100e1fb74aef68c95b>