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

On Fri, Sep 17, 2004 at 03:22:56PM +0100, Jonathan Larmour wrote:
> 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 :(.

Yep, i wound the comment in bugzilla.

Shouldn't it really be Alex who updates the list. He is the one
dealing with the papers and emailling the pdfs to the maintainers.

        Andrew

  reply	other threads:[~2004-09-17 14:26 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
2004-09-17 14:26     ` Andrew Lunn [this message]
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=20040917142556.GW26759@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@ecoscentric.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).