From owner-freebsd-current@FreeBSD.ORG  Fri Jan 11 20:42:05 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 600E9943;
 Fri, 11 Jan 2013 20:42:05 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net
 [IPv6:2001:470:1f10:75::2])
 by mx1.freebsd.org (Postfix) with ESMTP id 3BF24F74;
 Fri, 11 Jan 2013 20:42:05 +0000 (UTC)
Received: from ralph.baldwin.cx (c-68-39-198-164.hsd1.de.comcast.net
 [68.39.198.164])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 84E7DB993;
 Fri, 11 Jan 2013 15:42:04 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Subject: Re: [head tinderbox] failure on arm/arm
Date: Fri, 11 Jan 2013 11:16:06 -0500
User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; )
References: <201211082303.qA8N3RlN031977@freebsd-current.sentex.ca>
 <509D858C.6060005@gmail.com>
 <CAJ-VmonY1tLPpBGFDcthG4KGe_dCEFQMawBFQ1QnvKee=A2WYg@mail.gmail.com>
In-Reply-To: <CAJ-VmonY1tLPpBGFDcthG4KGe_dCEFQMawBFQ1QnvKee=A2WYg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201301111116.06531.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Fri, 11 Jan 2013 15:42:04 -0500 (EST)
Cc: Adrian Chadd <adrian@freebsd.org>, Chuck Burns <break19@gmail.com>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 20:42:05 -0000

On Friday, November 09, 2012 05:47:43 PM Adrian Chadd wrote:
> On 9 November 2012 14:37, Chuck Burns <break19@gmail.com> wrote:
> > Adrian. diskspace and cpu cycles are things I can spare, drop me a line
> > outside of the ML and we can discuss particulars. "It's just a personal
> > box.. on a residential internet service, I have an amd64 box with 600G
> > free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so
> > free, 512M ram..  just drop me a line..
> 
> Hi,
> 
> Those I do have - I have access to all of the ref* boxes in the
> cluster. I'm just typically hacking on this stuff on the train or at a
> cafe, and I don't have a workflow setup for pushing out potential
> diffs to build machines that have all the grunt/disk space for each
> little change that I do.
> 
> I'm sorry about breaking things from time to time, but besides a small
> handful of "what was I thinking?!" things, the build breaks are just
> that - build breaks. They're easily fixed.

This is why I use p4 branches.  I hack on my laptop and then commit it
to p4 and use 'p4 sync' as a glorified rsync on development hosts.  I can
then do a full 'make tinderbox' before committing to HEAD after extracting
the patches from p4 and applying them to an SVN checkout.  SVN branches
should let you do something similar as well (or just about any soure code
control system you choose to use).

-- 
John Baldwin