public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Andrew Lunn" <andrewlunn@fastmail.fm>
To: "Jonathan Larmour" <jifl@jifvik.org>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Patches not getting into the tree?
Date: Sat, 06 Jul 2002 13:48:00 -0000	[thread overview]
Message-ID: <20020706204811.A80396D9BC@www.fastmail.fm> (raw)

Hi Jifl

I understand the problem, and if i was not traveling around alaska i
would help out. 
Anyway, from a "marketing perspective", a constant trickle of patches
as apposed to none and then a flood, looks better. At the moment it
looks like eCos development is dead. Even an explanation to the delay
on ecos-patches may help.

If you are continuing with the RH copywrite assignemt i guess my
ftpclient patch is ok to go straight in. How does it normaly work for
other open source code? I thought that so long as the copywrite owner
was clearly stated in each file, it was not a problem, unless you
wanted to change the licence. Then you need to contact each person and
get the OK. Isn't that how Mozila did it?   

     Andrew

On Fri, 05 Jul 2002 18:54:28 +0100, "Jonathan Larmour"
<jifl@jifvik.org> said:
> Andrew Lunn wrote:
> > 
> > I guys
> > 
> > Whats happening about getting patches into the CVS tree? eg
> > 
> > http://sources.redhat.com/ml/ecos-patches/2002-06/msg00030.html
> > 
> > has not made it in yet. Is mailing to ecos-patches enough or do we need
> > to do more?
> 
> I intend to work on the backlog a bit. As well as being suckered into
> returning to Red Hat for my notice, my spare eCos time has been devoted
> to
> some book reviewing that's had a hard time limit on it. There's
> temporarily
> a hiatus, so I'll see what I can do.
> 
> For some of the outstanding patches though, we'll come back to
> copyright
> assignment requirements, and we don't have a good story on that yet.
> We'll
> have to go with RH assignments for now.
> 
> Jifl
> -- 
> --[ "You can complain because roses have thorns, or you ]--
> --[  can rejoice because thorns have roses." -Lincoln   ]--
> Opinions==mine
> 



-- 
http://fastmail.fm
 - Win a free email account: click here!

             reply	other threads:[~2002-07-06 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06 13:48 Andrew Lunn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-03 22:17 Andrew Lunn
2002-07-05 10:54 ` 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=20020706204811.A80396D9BC@www.fastmail.fm \
    --to=andrewlunn@fastmail.fm \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jifl@jifvik.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).