Path: ...!news.misty.com!.POSTED.veps.esmtp.org!not-for-mail From: Claus =?iso-8859-1?Q?A=DFmann?= Newsgroups: comp.mail.sendmail Subject: Re: FFRs Date: Wed, 22 Jan 2025 12:22:44 -0500 (EST) Organization: MGT Consulting Sender: Message-ID: References: <87ttcbly3k.fsf@example.com> <87ikqknjg1.fsf@miraculix.mork.no> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 22 Jan 2025 17:22:44 -0000 (UTC) Injection-Info: news.misty.com; posting-host="veps.esmtp.org:155.138.203.148"; logging-data="5826"; mail-complaints-to="abuse@misty.com" Mail-Copies-To: never X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: ca@x2.esmtp.org (Claus Assmann) Bytes: 1610 Lines: 13 Bjørn Mork wrote: > BTW; how many versions are the _FFR build options supposed to stay before > either being deprecated or made default? There's no rule for it. Some FFRs exist "forever", some are turned "on" within one release - usually the developers make a decision based on "perceived usefulness". -- Note: please read the netiquette before posting. I will almost never reply to top-postings which include a full copy of the previous article(s) at the end because it's annoying, shows that the poster is too lazy to trim his article, and it's wasting the time of all readers.