Date: Sat, 16 Mar 2002 11:53:09 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: sobomax@FreeBSD.org Cc: re@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: -CURRENT Feature Slush is OVER Message-ID: <20020316115309.E95652@dragon.nuxi.com> In-Reply-To: <1016289691.91096.2.camel@notebook>; from sobomax@mail.ru on Sat, Mar 16, 2002 at 04:43:47PM %2B0200 References: <20020316111818.GO17499@freebsdmall.com> <1016289691.91096.2.camel@notebook>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 16, 2002 at 04:43:47PM +0200, Maxim Sobolev wrote: > > primary goals in all of this are (1) to provide a usable preview of > > the 5.0-CURRENT code, and (2) to minimize the impact on -CURRENT > > developers. After evaluating several different options, using > > Perforce was deemed the best tool for the job. > > Could we have commit logs from the commits into that branch be sent to > cvs-all@, because otherwise most of the developers would be unable to > see what's going on there, which IMO is not a good thing. Why do we care? I already see the logs for -current. I don't really care what the RE's have to do in their branch to add the release-related things. 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?20020316115309.E95652>