Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #6 (deadline February 2)
Date: Tue, 21 Jan 2014 10:39:14 +0100	[thread overview]
Message-ID: <52DE4042.6060108@relinux.de> (raw)
In-Reply-To: <CAAXf6LX+8s0EC9itepQ2aoZK21AkTvQfDdoOa61aAqcwsJms5Q@mail.gmail.com>

On 21.01.2014 09:18, Thomas De Schampheleire wrote:
> Hi Stephan,
>
> On Tue, Jan 21, 2014 at 8:58 AM, Stephan Hoffmann <sho@relinux.de> wrote:
>> Am 20.01.2014 22:06, schrieb Thomas De Schampheleire:
>>> All,
>>>
>>> Here is session 6 of the patchwork cleanup. For those who haven't
>>> followed previous sessions, here is a quick recap: every session we'll
>>> be posting the list of the 10 oldest patches, with the original patch
>>> contributors in copy. During two weeks, we have the opportunity to
>>> discuss the patch, whether it is still necessary or not, how it should
>>> be changed to be merged.
>>>
>>> In particular, I'm interested in knowing if the original contributor is
>>> still interested by the patch, or if someone else is interested in
>>> adopting the patch and sending an updated version, or if the patch no
>>> longer makes sense due to other changes made in Buildroot.
>> .....
>>> ...
>>>
>>> Linux: enable local Linux tarball in config
>>> Stephan Hoffmann <sho@relinux.de>
>>> http://patchwork.ozlabs.org/patch/217204
>> Thomas, all,
>>
>> I still think that this would be a useful feature for buildroot,
>> especially when dealing with soc or boards that come with a kernel
>> tarball from the vendor that is not easily accessible online.
>>
> I just looked at your patch, but it is not needed to achieve what you
> want. If you specify:
> file:///path/to/local/file
> then the site method will be automatically set to file (just tested).
> Could you verify that this indeed fits your use case?
Yes, it does, and it does with the old buildroot I had then, too. So my
patch is obsolete, please remove it. I do not remember why I did not
find this last year.

Thanks

Stephan
>
> Thanks,
> Thomas


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de Stephan at reLinux.de

  reply	other threads:[~2014-01-21  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 21:06 [Buildroot] Patchwork oldest patches cleanup #6 (deadline February 2) Thomas De Schampheleire
2014-01-21  2:53 ` Przemyslaw Wrzos
2014-01-21  7:46   ` Thomas De Schampheleire
2014-01-23  3:43     ` Przemyslaw Wrzos
2014-01-21  7:58 ` Stephan Hoffmann
2014-01-21  8:18   ` Thomas De Schampheleire
2014-01-21  9:39     ` Stephan Hoffmann [this message]
2014-01-21 10:20       ` Thomas De Schampheleire
2014-01-21  9:02 ` Fabio Porcedda
2014-01-21  9:05   ` Thomas De Schampheleire
2014-01-22 22:10 ` Steve Calfee
2014-01-23 14:06   ` Thomas De Schampheleire
2014-01-27 20:07 ` Thomas De Schampheleire
2014-02-03  9:52   ` Thomas De Schampheleire

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=52DE4042.6060108@relinux.de \
    --to=sho@relinux.de \
    --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