Satoshi.
On Mon, Jul 12, 1999 at 12:31:52AM -0700, Satoshi - Ports Wraith - Asami wrote:
> * From: Nik Clayton <[EMAIL PROTECTED]>
>
> I really wish you would stop spreading FUD. Don't open your mouth if
> you don't know what you are talking about.
I do know what I'm talking about -- specifically;
> * I was under the impression that if you were CVSup'ing the ports tree then
> * any changes to the ports subsystem (for example, new command line
> * parameters to fetch(1)) would be utilised by the ports system *before*
> * they had been merged in to -stable. The rationale being that if you
> * were tracking the ports tree in that way then you should be tracking
> * -current instead.
I'm careful to state that it's my impression. Not that it's the gospel
truth, but that's the 'vibe' I've picked up from the times when the ports
and src trees have been out of sync, and I've gone scouring for answers
as to what's happened.
You're correct in that better awareness is almost definitely the key.
Would you consider posting the -stable and -current port build results
to -announce (and comp.unix.bsd.freebsd.announce) fortnightly, in the
same way that the "New ports committed in the past two weeks" message
is sent out?
N
--
[intentional self-reference] can be easily accommodated using a blessed,
non-self-referential dummy head-node whose own object destructor severs
the links.
-- Tom Christiansen in <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
