Date: Tue, 4 Aug 2009 21:32:07 +0000 From: "b. f." <bf1783@googlemail.com> To: freebsd-questions@FreeBSD.org Subject: Re: cvs tag usage Message-ID: <d873d5be0908041432v75b53271ue578b727409bd21d@mail.gmail.com> In-Reply-To: <4ad871310908041334k43cb70e2t572276edcf0caee7@mail.gmail.com> References: <d873d5be0908041254x710b250sca7c2eea71b0f4a9@mail.gmail.com> <4ad871310908041334k43cb70e2t572276edcf0caee7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/4/09, Glen Barber <glen.j.barber@gmail.com> wrote: >> >>>> _7_2_0_RELEASE >>> >>>Should be RELENG. Don't blindly follow how-tos. >>> >> >> RELENG_7_2_0_RELEASE is a valid tag. Don't make pronouncements if you >> haven't verified them. >> > > He has _7_2_0_RELEASE, not RELENG_7_0_2_RELEASE. Well, neither actually. :) s/0_2/2_0/ . But I inferred from the context -- it seemed obvious, particularly from what he wrote later -- that he meant those choices as suffixes to RELENG, which he omitted for the sake of brevity. I assumed you also made this inference. ... Mel Flynn wrote: > >And for developers or interesting parties, one can create cvs diff using >-rRELENG_7_2_BP -rRELENG_7_2_RELEASE to see how many fixes hit the tree during >the final release stage. How many "interesting parties" have you been to, Mel, where such a listing came in handy? ;)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d873d5be0908041432v75b53271ue578b727409bd21d>