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] [PATCH 2/4 v2] tools: move test-pkg out of support/scripts
Date: Sun, 18 Jun 2017 16:16:19 +0200	[thread overview]
Message-ID: <20170618141619.GR2918@scaer> (raw)
In-Reply-To: <20170618161243.04768757@windsurf>

Thomas, All,

On 2017-06-18 16:12 +0200, Thomas Petazzoni spake thusly:
> On Sun, 18 Jun 2017 16:01:43 +0200, Yann E. MORIN wrote:
> >  docs/manual/adding-packages-tips.txt |  12 +--
> >  support/scripts/test-pkg             | 198 +----------------------------------
> >  tools/00-README.txt                  |   5 +
> >  tools/test-pkg                       | 197 ++++++++++++++++++++++++++++++++++
> >  4 files changed, 209 insertions(+), 203 deletions(-)
> >  mode change 100755 => 120000 support/scripts/test-pkg
> >  create mode 100755 tools/test-pkg
> 
> No strong opinion on whether such a move is desirable,

That was a proposal by Arnout:
    http://lists.busybox.net/pipermail/buildroot/2016-October/174290.html

> but at the very
> list I believe we should not add this 00-README.txt file. Nowhere else
> in the tree we have files named like this, and I don't think we should
> start adding these.

I'm OK for dropping it.

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:[~2017-06-18 14:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 14:01 [Buildroot] [PATCH 0/4 v2] tools: add a directory to contain usefull user-facing tools Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 1/4 v2] tools: add a directory to store some useful " Yann E. MORIN
2017-06-19  1:11   ` Ricardo Martincoski
2017-06-19 15:42     ` Yann E. MORIN
2017-06-21  2:06       ` Ricardo Martincoski
2017-06-21  5:21         ` Yann E. MORIN
2017-06-21 21:44           ` Arnout Vandecappelle
2017-06-22 19:18             ` Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 2/4 v2] tools: move test-pkg out of support/scripts Yann E. MORIN
2017-06-18 14:12   ` Thomas Petazzoni
2017-06-18 14:16     ` Yann E. MORIN [this message]
2017-06-22  7:57     ` Arnout Vandecappelle
2017-06-22  8:13       ` Thomas Petazzoni
2017-06-22  8:30         ` Arnout Vandecappelle
2017-06-22 19:20           ` Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 3/4 v2] tools: move get-developers out of support/scripts/ Yann E. MORIN
2017-06-18 14:01 ` [Buildroot] [PATCH 4/4 v2] tools: move check-package " Yann E. MORIN
2017-06-19  1:13   ` Ricardo Martincoski
2017-06-19 18:46     ` Yann E. MORIN
2017-06-19  3:22   ` Ricardo Martincoski
2017-06-19 18:48     ` Yann E. MORIN
2017-06-19 20:27       ` Ricardo Martincoski
2017-06-18 14:15 ` [Buildroot] [PATCH 0/4 v2] tools: add a directory to contain usefull user-facing tools Thomas Petazzoni
2017-06-18 14:23   ` Yann E. MORIN
2017-06-21 22:04     ` Arnout Vandecappelle

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=20170618141619.GR2918@scaer \
    --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