[Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB)

Pieter Smith pieter at boesman.nl
Sun Apr 24 08:47:58 UTC 2016


Hi Thomas,

On Sun, Apr 24, 2016 at 10:32:11AM +0200, Pieter Smith wrote:
> Hi Thomas,
> 
> On Sun, Apr 24, 2016 at 10:16:53AM +0200, Thomas Petazzoni wrote:
> > Hello,
> > 
> > On Sun, 24 Apr 2016 10:04:07 +0200, Pieter Smith wrote:
> > 
> > > I will post the patch series including the beaglebone_barebox_defconfig. This
> > > will at least illustrate usage, even if it only lives in the mailing archives.
> > > Should it be required: The buildroot maintainers have my permission to merge
> > > only a sub-set of the patch-series. I do not object to this, and I will make it
> > > clear in the summary.
> > 
> > It is in any case very useful to include a defconfig in the series to
> > ease testing. Another possibility is to include the defconfig used for
> > testing inside one of the commit log, so that it remains part of the
> > Git history, and easily available if one looks at the Git commits
> > touching the barebox package.
> 
> Augment the last message in the series with the defconfig? Easy enough. Will be
> in v5. Or would you like something fancy (E.g. empty commit)?

The largest part of the barebox defconfig is the post-image scripting and
barebox environment tuning totalling 4 additional files. Should I add these to
the commit-log as well?

[snip]

- Pieter




More information about the buildroot mailing list