From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package: drop games/ subdir
Date: Mon, 05 Nov 2012 14:28:27 +0200 [thread overview]
Message-ID: <5097B0EB.9060108@petroprogram.com> (raw)
In-Reply-To: <5097AE66.1080607@mind.be>
5.11.2012 14:17, Arnout Vandecappelle kirjoitti:
> On 11/05/12 12:23, Stefan Fr?berg wrote:
>> 5.11.2012 9:23, Peter Korsgaard kirjoitti:
>>> commit:
>>> http://git.buildroot.net/buildroot/commit/?id=9b809e1a6ad2a82bfe0d2383f69f45ae8c6283bb
>>> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>>>
>>> As discussed during the dev day.
>
> Looks like I was distracted when it was discussed, because I didn't
> write it in the
> report. But that's probably not really needed anymore...
>
> [snip]
>> Aww...
>>
>> And I had just finished porting dosbox, DOS emulator that can run old
>> classic DOS games
>> and programs, to buildroot.
>>
>> No games for buildroot developers/users then ?
>
> It just moved out of the games/ subdirectory, e.g. package/doomwad
> instead of
> package/games/doomwad.
>
> The general idea is that the subdirectories are confusing and we want
> to get
> rid of them.
>
Ah, I see.
Well, you are right.
They can be a little confusing.
For example, when I start porting some fresh stuff to buildroot the
first thing I usually do is just throw them under the dir named "hacking"
:D
And only afterwards I start wondering what belongs to what subdir.
Best regards
Stefan
> Regards,
> Arnout
>
prev parent reply other threads:[~2012-11-05 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 7:23 [Buildroot] [git commit] package: drop games/ subdir Peter Korsgaard
2012-11-05 11:23 ` Stefan Fröberg
2012-11-05 12:17 ` Arnout Vandecappelle
2012-11-05 12:28 ` Stefan Fröberg [this message]
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=5097B0EB.9060108@petroprogram.com \
--to=stefan.froberg@petroprogram.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