public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: HOWTO: eCos on QEMU PC emulator
Date: Fri, 25 Mar 2011 15:27:00 -0000	[thread overview]
Message-ID: <AANLkTim-krvfUPpEDNw_+c79Q_SoHEx61HX5MAHGo40W@mail.gmail.com> (raw)
In-Reply-To: <imiak6$i3e$3@dough.gmane.org>

On Fri, Mar 25, 2011 at 3:59 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2011-03-25, Drasko DRASKOVIC <drasko.draskovic@gmail.com> wrote:
>
>> I am very interested about this...
>>
>> First - can not you re-distribute eCos code as you like ?
>
> You have to follow the license terms, but they are pretty liberal
Yes, I meant giving it publicly, following the licence.


>> Second, if you re-distribute it, can not you do it the way you like -
>> for example putting it in git repository.
>
> Yes, you certainly can.

So why then the authors must assign copyright to the FSF and
contribute it in the order for us to put eCos sources in git tree ?

BR,
Drasko

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2011-03-25 15:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 11:11 [ECOS] " Grant Edwards
2011-03-24 12:34 ` Drasko DRASKOVIC
2011-03-24 16:26   ` [ECOS] " Grant Edwards
2011-03-24 16:44     ` Drasko DRASKOVIC
2011-03-24 16:48       ` Grant Edwards
2011-03-24 17:06         ` Grant Edwards
2011-03-24 17:12           ` John Dallaway
2011-03-24 17:19             ` Drasko DRASKOVIC
2011-03-24 17:41               ` Sergei Gavrikov
2011-03-24 21:30               ` John Dallaway
2011-03-24 17:59             ` Grant Edwards
2011-03-24 18:17               ` Sergei Gavrikov
2011-03-24 18:26                 ` Sergei Gavrikov
2011-03-24 18:44                   ` Grant Edwards
2011-03-24 18:51                     ` Sergei Gavrikov
2011-03-24 19:06                       ` Grant Edwards
2011-03-24 19:16                         ` Sergei Gavrikov
2011-03-24 19:48                           ` Grant Edwards
2011-03-25  8:26                             ` Sergei Gavrikov
2011-03-24 22:19               ` John Dallaway
2011-03-25 14:10                 ` Grant Edwards
2011-03-24 17:11     ` Drasko DRASKOVIC
2011-03-24 17:20       ` Grant Edwards
2011-03-24 17:45         ` Drasko DRASKOVIC
2011-03-25 14:48   ` Grant Edwards
2011-03-25 14:50     ` Drasko DRASKOVIC
2011-03-25 15:00       ` Grant Edwards
2011-03-25 15:02         ` Drasko DRASKOVIC
2011-03-25 15:17           ` ricky wu
2011-03-25 15:24           ` Grant Edwards
2011-03-25 15:27             ` Drasko DRASKOVIC [this message]
2011-03-25 15:37               ` John Dallaway
2011-03-24 13:18 ` [ECOS] " Stanislav Meduna
2011-03-24 14:21   ` Drasko DRASKOVIC
2011-03-24 14:46     ` Stanislav Meduna
2011-03-24 16:08       ` Drasko DRASKOVIC
2011-03-29 12:01 [ECOS] " Alex Schuilenburg
2011-03-29 12:56 ` Grant Edwards
     [not found]   ` <AANLkTi=2DOgy7xpyGBnbvf5gEfM2kE6PRDcyCqzyUM7b@mail.gmail.com>
2011-03-29 23:09     ` ricky wu

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=AANLkTim-krvfUPpEDNw_+c79Q_SoHEx61HX5MAHGo40W@mail.gmail.com \
    --to=drasko.draskovic@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=grant.b.edwards@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).