Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Aug 2006 21:41:59 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        silby@silby.com
Cc:        cvs-src@freebsd.org, itetcu@freebsd.org, src-committers@freebsd.org, cognet@freebsd.org, cvs-all@freebsd.org
Subject:   Re: __FreeBSD_version was: Re: cvs commit: src/sys/sys _timeval.h user.h src/sys/arm/include _types.h
Message-ID:  <20060819.214159.1723235838.imp@bsdimp.com>
In-Reply-To: <20060819200148.S952@odysseus.silby.com>
References:  <20060624115603.25c962bc@it.buh.tecnik93.com> <20060624.162505.1678771172.imp@bsdimp.com> <20060819200148.S952@odysseus.silby.com>

index | next in thread | previous in thread | raw e-mail

In message: <20060819200148.S952@odysseus.silby.com>
            Mike Silbersack <silby@silby.com> writes:
: 
: On Sat, 24 Jun 2006, M. Warner Losh wrote:
: 
: > : I don't believe you should relay on being the only user.
: > : At least please bump __FreeBSD_version.
: >
: > I'm pretty sure that he is the only FreeBSD/arm user that's using
: > RELENG_6 :-).  We're using current at work, but will soon transition
: > to RELENG_6, now that these patches have been MFC'd.  Of course, it
: > wouldn't hurt to at least document this change in the sequence of
: > version bumps on the 6.x timeline.  But the number of people affected
: > can be counted on one hand, with fingers left over.
: >
: > Warner
: 
: Maybe this has been discussed in the past, but why don't we just have 
: __FreeBSD_version auto-incremented every day?  It would be great for 
: situations where we currently use it, and it's also be great for bug 
: reports.

That's been discussed to death, but you can't use the results of
'date' to do it, and it causes horrible repo churn if you commit a
change like this every day to multiple branches.  In short, it sounds
good, but when you go to actually implement you discover that it
really is lame.

Warner


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060819.214159.1723235838.imp>