From: Marc Leeman <marc.leeman@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] GPL Licensing issues
Date: Mon, 27 Sep 2004 10:24:00 +0200 [thread overview]
Message-ID: <1f729c4804092701245a77ded9@mail.gmail.com> (raw)
In-Reply-To: <20040927072903.4A979C1430@atlas.denx.de>
> Header files contain interfaces, not code.
> Code is in source files per definition :-)
In an ideal world with decent programmers, they are :)
In a something less than ideal world where ppl are bent on *cough*
optimising *cough* the code for reasons they only know, code can be
found anywhere...
Don't get me wrong, I fully agree with you, but in an environment
where engineers with an exclusive FPGA and hardware background write C
'firmware', one tends to see all kinds of code organisations :-/
As such, making the difference between *.c and *.h might not be the
best solution. But this is the OS vs FS software discussion again in
which I am not yet fully decided (I think)...
--
ash nazg durbatul?k, ash nazg gimbatul,
ash nazg thrakatul?k agh burzum-ishi krimpatul
next prev parent reply other threads:[~2004-09-27 8:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 20:29 [U-Boot-Users] U-Boot not responding back to ARP requests? Robin Getz
2004-09-26 22:47 ` Wolfgang Denk
2004-09-27 0:54 ` [U-Boot-Users] GPL Licensing issues Robin Getz
2004-09-27 6:27 ` Marc Leeman
2004-09-27 7:28 ` Wolfgang Denk
2004-09-27 8:24 ` Marc Leeman [this message]
2004-09-27 10:29 ` Marius Groeger
2004-09-27 11:12 ` Marc Leeman
2004-09-27 12:40 ` Doug Kehn
2004-09-27 20:20 ` Wolfgang Denk
2004-09-27 7:22 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 8:04 Robin Getz
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=1f729c4804092701245a77ded9@mail.gmail.com \
--to=marc.leeman@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.