From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Wed, 22 Oct 2014 08:16:52 -0700 Subject: [U-Boot] [PATCH v10 14/14] RFC: Deprecate MAKEALL In-Reply-To: References: <1409240626-6924-3-git-send-email-sjg@chromium.org> <1409240626-6924-15-git-send-email-sjg@chromium.org> <20141014081724.GF25506@bill-the-cat> <20141022083327.EEE7F3834D1@gemini.denx.de> Message-ID: <5447CA64.3050901@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 10/22/2014 08:11 AM, Simon Glass wrote: > Hi Wolfgang, > > On 22 October 2014 02:33, Wolfgang Denk wrote: >> Dear Tom, >> >> In message <20141014081724.GF25506@bill-the-cat> you wrote: >>> >>> No, not yet. I am going to mention in the release notes that we're >>> going to strongly start thinking about deleting MAKEALL. We can pick up >>> the deprecation patch early in the next merge window. >> >> Can we please keep at least some script (as a wrapper around >> buildman?) that keeps the old user interface in place? >> >> I frequently use "git bisect run MAKEALL ...", and it would >> be nice if we could keep this working even in newer versions of the >> code. >> >> Or is there a similar alternative command that works with identical >> parameters for - say - all versions of the last two years or so? > > Unfortunately there is not really an equivalent, and buildman only recently > > - sets its return code correctly > - supports building the current tree (previously it required a branch > name for the commit to build) > > During development of buildman/patman I used to keep a separate tree. > Then you can run the latest buildman from that tree using you current > directory for the bisect. > > I could perhaps look at adjusting MAKEALL to call buildman if that > solution isn't good enough (this will work assuming that buildman has > been set up with toolchains, etc.). Still I think a deprecation > warning is a good start. > Simon, While you work on buildman, please consider to regenerate boards.cfg for each build. If one patch in a series adds a board, there will be a false error for patches before it. York