Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] fs: allow filesystems to set the name of their output file
Date: Sat, 3 Nov 2018 20:25:41 -0200 (BRST)	[thread overview]
Message-ID: <1338398979.26630.1541283941592.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <400754389.13590.1541211606004.JavaMail.zimbra@datacom.com.br>

> From: "DATACOM" <casantos@datacom.com.br>
> To: "Yann Morin" <yann.morin.1998@free.fr>
> Cc: "buildroot" <buildroot@buildroot.org>
> Sent: Sexta-feira, 2 de novembro de 2018 23:20:06
> Subject: Re: [Buildroot] [PATCH v2] fs: allow filesystems to set the name of their output file

>> From: "Yann Morin" <yann.morin.1998@free.fr>
>> To: "DATACOM" <casantos@datacom.com.br>
>> Cc: "buildroot" <buildroot@buildroot.org>
>> Sent: Quinta-feira, 1 de novembro de 2018 18:01:03
>> Subject: Re: [PATCH v2] fs: allow filesystems to set the name of their output
>> file
> 
>>> +ROOTFS_$(2)_FINAL_IMAGE_NAME = $$(call qstrip,$$(ROOTFS_$()_IMAGE_NAME))
>>                                                           ^^^
>> 
>> This patch has not been tested at all, it can't even possibly work...
> 
> Pfff, I will send a follow-up fixing that. Sorry.
> 
> Scratching my head attempting to find how it happened.

FYI: I figured out the reason why the buggy patch was sent but I won't
tell ya because it is too much embarrassing. :-(

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer

  reply	other threads:[~2018-11-03 22:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  2:31 [Buildroot] [RFC] fs: allow passing the image file name to inner-rootfs Carlos Santos
2018-10-21 13:26 ` Yann E. MORIN
2018-10-24  1:01   ` [Buildroot] [PATCH] fs: allow filesystems to set the name of their output file Carlos Santos
2018-10-24 14:36     ` Yann E. MORIN
2018-10-25  0:20       ` [Buildroot] [PATCH v2] " Carlos Santos
2018-11-01 21:01         ` Yann E. MORIN
2018-11-03  2:20           ` Carlos Santos
2018-11-03 22:25             ` Carlos Santos [this message]
2018-11-03 22:13         ` Carlos Santos
2018-11-03 10:37       ` [Buildroot] [PATCH] " Arnout Vandecappelle
2018-11-03 13:34         ` Yann E. MORIN
2018-11-03 22:09           ` Carlos Santos
2018-11-30 18:18             ` Yann E. MORIN
2018-10-25  0:23     ` Carlos Santos
2018-10-24  1:04   ` [Buildroot] [RFC] fs: allow passing the image file name to inner-rootfs Carlos Santos

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=1338398979.26630.1541283941592.JavaMail.zimbra@datacom.com.br \
    --to=casantos@datacom.com.br \
    --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