From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gstreamer1: use a relative symlink to gstconfig.h
Date: Fri, 29 Jan 2016 15:16:55 +0100 [thread overview]
Message-ID: <20160129151655.529f1cd1@free-electrons.com> (raw)
In-Reply-To: <CAHXCMMJPDbJCDFGoT958z+52j=zXjxy0ZUQFafvMr8u9YpuneQ@mail.gmail.com>
Hello Samuel,
On Fri, 29 Jan 2016 14:33:23 +0100, Samuel Martin wrote:
> I'm working on making the SDK (host dir. and staging dir.) relocatable.
> You can check the current state of my branch [1].
> I hope to submit a first step before the 2016.02 RC month, but this is
> not yet ready :-/
>
> Anyway, I'm really interested in gathering all that have to be done
> for the relocatable SDK. ;-)
Glad to hear you are working on making the SDK relocatable !
However, if I may have a suggestion, I believe you shouldn't submit all
the changes needed in one big patch series.
Instead, what I would suggest is that you:
1/ Write up a web-page or Wiki-page with a list of things that need to
be fixed.
2/ Send one patch series for each thing that needs to be fixed. And
maybe not send all patch series at the same time: handle one or two
topics at a time.
3/ Keep your Wiki page updated with the things that have been merged,
and things that remain to be merged, that remain to be submitted,
etc.
Moving to a relocatable SDK is a big change that requires lots of
smaller changes. We have to handle it progressively, otherwise it will
never be merged due to the amount of required changes.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-29 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:19 [Buildroot] [PATCH 1/1] gstreamer1: use a relative symlink to gstconfig.h Phil Eichinger
2016-01-28 16:55 ` Peter Korsgaard
2016-01-29 13:10 ` Phil Eichinger
2016-01-29 13:33 ` Samuel Martin
2016-01-29 14:16 ` Thomas Petazzoni [this message]
2016-01-31 19:50 ` 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=20160129151655.529f1cd1@free-electrons.com \
--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