This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [BUILDROBOT][PATCH] frv-linux fallout (was: [PATCH 009/236] Replace BB_HEAD et al macros with functions)
- From: Mike Stump <mikestump at comcast dot net>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: Jan-Benedict Glaw <jbglaw at lug-owl dot de>, Nick Clifton <nickc at redhat dot com>, Alexandre Oliva <aoliva at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 25 Aug 2014 12:29:41 -0700
- Subject: Re: [BUILDROBOT][PATCH] frv-linux fallout (was: [PATCH 009/236] Replace BB_HEAD et al macros with functions)
- Authentication-results: sourceware.org; auth=none
- References: <1407345815-14551-1-git-send-email-dmalcolm at redhat dot com> <1407345815-14551-10-git-send-email-dmalcolm at redhat dot com> <20140823184932 dot GG12042 at lug-owl dot de> <1408975689 dot 24896 dot 20 dot camel at surprise>
On Aug 25, 2014, at 7:08 AM, David Malcolm <dmalcolm@redhat.com> wrote:
>
> I'm testing and committing individual patches, but this
> could have gone into trunk in one go.
Yeah, it’s a hard choice between bit rot and incrementally going in.
> what I realize now is that I should have
> continued rebasing my patches in git until they were ready to go... but
> then committed them to a svn branch, with a ChangeLog.rtx-classes, and
> *immediately* merged that branch to trunk.
If you go all in at once, you forgot to list the build just after checkin. :-) Most work doesn’t require it, but for larger work, it is nice to build post checkin and resolve build errors, if any, when there are any changes from trunk post the last build.
> It's too late now to switch to this approach, so in the meantime I've
> been working on ways to make my bootstraps as fast as possible.
-j64 works wonders. :-) Though, it is annoying watching the build run at 98% idle.