From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3
Date: Tue, 9 Jan 2018 10:56:28 +0100 [thread overview]
Message-ID: <20180109105628.6bd70119@windsurf> (raw)
In-Reply-To: <20171217050554.5377c971@windsurf>
Hello Carlos,
On Sun, 17 Dec 2017 05:05:54 +0100, Thomas Petazzoni wrote:
> On Sat, 16 Dec 2017 17:53:12 -0200 (BRST), Carlos Santos wrote:
>
> > > I will try it. Meanwhile we need a temporary solution.
> >
> > BTW, I their current naming scheme is already reasonable, since each
> > release use a separate path. Those who download the file can save it
> > with a different name. That's not rocket science.
>
> Except it's totally uncommon, and many people save tarballs in a single
> folder. What they do is contrary to the practice of pretty much every
> other open-source project.
In the end, did you get the chance to raise the issue of the tarball
name with the upstream developers ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-09 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 15:38 [Buildroot] [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3 Carlos Santos
2017-12-15 15:38 ` [Buildroot] [PATCH v2 2/2] iqvlinux: add patch to support Linux kernel 4.12 and later Carlos Santos
2017-12-15 15:38 ` [Buildroot] FW: " Kees van Unen
2017-12-15 15:38 ` [Buildroot] FW: [PATCH v2 1/2] iqvlinux: bump to version 1.2.0.3 Kees van Unen
2017-12-16 14:50 ` [Buildroot] " Thomas Petazzoni
2017-12-16 19:03 ` Carlos Santos
2017-12-16 19:53 ` Carlos Santos
2017-12-17 4:05 ` Thomas Petazzoni
2018-01-09 9:56 ` Thomas Petazzoni [this message]
2018-01-10 1:56 ` Carlos Santos
2018-02-14 11:38 ` Carlos Santos
2018-02-14 12:38 ` Thomas Petazzoni
2018-02-14 19:37 ` Carlos Santos
2018-02-14 19:46 ` Thomas Petazzoni
2018-04-01 22:37 ` Thomas Petazzoni
2018-04-03 3:29 ` Carlos Santos
2018-04-02 9:26 ` Thomas Petazzoni
2018-04-03 3:29 ` 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=20180109105628.6bd70119@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--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