public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Andrea Michelotti <amichelotti@atmelroma.it>,
	ecos-maintainers@ecos.sourceware.org
Subject: Re: jtst ecos porting
Date: Fri, 17 Sep 2004 14:23:00 -0000	[thread overview]
Message-ID: <414AF340.1000300@eCosCentric.com> (raw)
In-Reply-To: <20040917105150.GS26759@biferten.ma.tech.ascom.ch>

Andrew Lunn wrote:
> On Fri, Sep 17, 2004 at 12:42:41PM +0200, Andrea Michelotti wrote:
> 
>>Hi Jonathan,
>>I re-posted jtst ecos porting patch to you, I aligned it with the current
>>status of cvs.
>>But it's becoming difficult to follow ATMEL sites and some customer that ask
>>updated version of eCos with the jtst port.
>>I know you are very very busy; I would like only to know (to do my
>>schedules) when do you think this port could be integrated into CVS.
> 
> 
> Hi Andrea
> 
> How does this port stand in terms of copyright transfer? You or Atmel
> are not apper on our list of people with copyright agreements. 
> 
> Please could you take a look at http://ecos.sourceware.org/assign.html

The assignment is okay, I hadn't updated the assignment list :(.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  parent reply	other threads:[~2004-09-17 14:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 10:38 Andrea Michelotti
2004-09-17 10:52 ` Andrew Lunn
2004-09-17 11:07   ` Andrea Michelotti
2004-09-17 14:23   ` Jonathan Larmour [this message]
2004-09-17 14:26     ` Andrew Lunn
2004-09-17 14:36 ` Jonathan Larmour
2004-09-17 14:40   ` Andrew Lunn
2004-09-17 15:20     ` Jonathan Larmour

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=414AF340.1000300@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=amichelotti@atmelroma.it \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    /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).