Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #5 (deadline January 19)
Date: Mon, 20 Jan 2014 22:20:33 +0100	[thread overview]
Message-ID: <20140120212033.GB3421@free.fr> (raw)
In-Reply-To: <CAAXf6LVP6OkzizTdx1GV8wc1vOUBr6Q9eRVQY7dYvK=14qj7=w@mail.gmail.com>

Thomas, All,

On 2014-01-20 21:37 +0100, Thomas De Schampheleire spake thusly:
> On Sun, Jan 5, 2014 at 6:17 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Thomas, Floris, All,
> >
> > On 2014-01-05 17:20 +0100, Yann E. MORIN spake thusly:
> >> On 2014-01-05 17:01 +0100, Thomas De Schampheleire spake thusly:
> >> > Here is the session 5 of the patchwork cleanup.
> > [--SNIP--]
> >> > [1/2] makebootfat: new package
> >> > Floris Bos <bos@je-eigen-domein.nl>
> >> > http://patchwork.ozlabs.org/patch/213112
> >>
> >> I'm not sure we need that one. We already have:
> >>   - host-dosfstools to generate (empty) fat filesystems in a image file;
> >>   - host-mtools to add files to a fat filesystem, and it works with
> >>     image files.
> >
> > It seems I've spoken a bit fast on that one. There's one thing this
> > package provides that is not provided by dosfstools or mtools: an MBR
> > bootcode.
> >
> > However, we already have syslinux, which does provide an MBR bootcode.
> > It's currently not installed; it's just a matter of adding one more
> > option to syslinux, to install its MBR bootcode.
> >
> > So, my previous position still stands: we already have the required
> > packages; no need to duplicate what we already have.
> 
> For me this conclusion is fine.
> There is a second patch in that same series:
> http://patchwork.ozlabs.org/patch/213113/
> [2/2] Basic filesystem image with partition table support
> 
> which sounds a lot like your 'fs/custom' patch series. If you agree, I
> propose to also reject that second patch since fs/custom is a more
> generic solution to the same problem.

I've had only a quick look at that patch, and it is limited to building
MBR-based images, indeed.

Not because I'm the author (Ok, a bit becasue I'm the author), I'd
prefer we work to merge genimages, since it is more generic, already
supports MBR and GPT, and is more easily extendable to other formats.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-01-20 21:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 16:01 [Buildroot] Patchwork oldest patches cleanup #5 (deadline January 19) Thomas De Schampheleire
2014-01-05 16:03 ` Thomas De Schampheleire
2014-01-05 16:25   ` Yann E. MORIN
2014-01-05 16:20 ` Yann E. MORIN
2014-01-05 17:17   ` Yann E. MORIN
2014-01-20 20:37     ` Thomas De Schampheleire
2014-01-20 21:20       ` Yann E. MORIN [this message]
2014-01-09 20:40   ` Yann E. MORIN
2014-01-20 20:44     ` Thomas De Schampheleire
2014-01-06 13:45 ` Matthew Weber
2014-01-20 20:43   ` Thomas De Schampheleire
2014-01-18 15:35 ` Thomas De Schampheleire
2014-01-20 20:58 ` Thomas De Schampheleire
2014-01-28 19:56   ` Thomas Petazzoni
2014-02-03  9:43     ` Thomas De Schampheleire
2014-02-04  9:34       ` Thomas De Schampheleire

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140120212033.GB3421@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox