From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <8b32503b37edf61a926866d7abdc4606@brasstown.quanstro.net>
References: <20130323100519.GA3980@polynum.com>
	<C9DC5E89-066D-484B-BE3C-9089C05DFF38@lsub.org>
	<CAKzdPgzpf9e6fVMjxKp9zjXZ9xxVaVgPpz6bbqCAg=EiDfotRg@mail.gmail.com>
	<1978071.ShBtZ0rfsK@coil>
	<2087087D-B83B-43EE-8CA9-D3B578C91938@gmail.com>
	<8b32503b37edf61a926866d7abdc4606@brasstown.quanstro.net>
Date: Mon, 25 Mar 2013 08:38:07 -0600
Message-ID: <CAK4xykWPM2DBYt2Sv-yLNHa02XnyN8TgF_sza8NvgVJzFZdJ-A@mail.gmail.com>
From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] mk and transitive dependencies (was: gcc not an option
 for Plan9)
Topicbox-Message-UUID: 34acb2f4-ead8-11e9-9d60-3106f5b1d025

> neither is a big issue in practice.  but that leads me to an interesting
> question, does go rebuild everything if the go compiler has changed?

i think it stops at package "runtime". at least that's what it builds
first when I tell it to "rebuild everything".