From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/avenger96_defconfig: add support for Arrow Avenger96 board
Date: Sun, 07 Feb 2021 22:09:10 +0200 [thread overview]
Message-ID: <87blcvy715.fsf@tarshish> (raw)
In-Reply-To: <a86ec3d8-17d5-bd4d-d6e9-f0d29071eeb4@grinn-global.com>
Hi Bartosz,
On Sun, Feb 07 2021, Bartosz Bilas wrote:
> On 2/7/21 6:00 PM, Baruch Siach wrote:
>> On Sun, Feb 07 2021, Yann E. MORIN wrote:
>>> On 2021-02-07 18:09 +0200, Baruch Siach spake thusly:
>>>> On Sun, Feb 07 2021, Peter Korsgaard wrote:
>>>>> + $ sudo dd if=output/images/sdcard.img of=/dev/sdX
>>>> Maybe warn that this overwrites data on the SD card.
>>> As far as I could see, we don't do that in any of the 72 readme.txt we
>>> already have...
>> $ git grep WARNING -- board/
>> ...
>> board/chromebook/elm/readme.txt:WARNING: make sure there is nothing important on that card,
>> board/chromebook/snow/readme.txt:WARNING: make sure there is nothing important on that card,
>> board/engicam/geam6ul/readme.txt:*** WARNING! This will destroy all the card content. Use with care! ***
>> ...
>>
> Is not that obvious that dd will overwrite the data? Imo it's superfluous
> information at all.
It might be obvious to you. Many newcomers don't know what dd is, or how
filesystem works. A warning can't hurt.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2021-02-07 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 15:55 [Buildroot] [PATCH] configs/avenger96_defconfig: add support for Arrow Avenger96 board Peter Korsgaard
2021-02-07 16:09 ` Baruch Siach
2021-02-07 16:52 ` Yann E. MORIN
2021-02-07 17:00 ` Baruch Siach
2021-02-07 17:52 ` Bartosz Bilas
2021-02-07 20:09 ` Baruch Siach [this message]
2021-02-07 20:44 ` Yann E. MORIN
2021-02-07 22:12 ` Peter Korsgaard
2021-02-07 21:49 ` Peter Korsgaard
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=87blcvy715.fsf@tarshish \
--to=baruch@tkos.co.il \
--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