Re: mq_timed... sem_timedwait, pthread_mutex_timed_lock

[Dmitriy Korovkin <dkorovkin at rambler dot ru>]

Jonathan, 
I have several questions, some of them, I'm afraid are because of my 
English. Please, be patient.
1. Did I understand you correctly that I'm allowed to do "cvs update" and 
check in changes into the eCos CVS tree?
2. Not a question, but I'll discuss the agreement with my bosses.
3. I have seen "Contributions and Third Party Projects". Is it possible 
for our company (Tecon Inc.) to be included into this list as a company 
made an ISaGRAF Pro port to eCos?

Thank you in advance,
-- 
Dmitriy

On Wed, 22 Jan 2003, Jonathan Larmour wrote:

> Date: Wed, 22 Jan 2003 04:37:07 +0000
> From: Jonathan Larmour <jifl@eCosCentric.com>
> To: Dmitriy Korovkin <dkorovkin@rambler.ru>
> Cc: ecos-patches@sources.redhat.com
> Subject: Re: mq_timed... sem_timedwait, pthread_mutex_timed_lock
> 
> Dmitriy Korovkin wrote:
> > Hi,
> > I'm really sorry about my previous patch. I has many stupied bugs and 
> > typos. Here is the fixed one. At least, I could start ISaGRAF target using 
> > this patch. Would please, review it.
> 
> Okay, although I'd appreciate Nick's ok in principle for the addition of a 
> mutex timed lock - it's exactly the correct thing to do, but just in case.
> 
> But I'd really rather you submitted the patch with the stuff already 
> applied taken out. As you have the originals from which the below were 
> taken, it is far easier for you to do a "cvs update" and merge in your 
> changes, than for us to work out the rejects after applying patch.
> 
> Could you do that please?
> 
> I also believe that despite a lot of the code being derived from 
> elsewhere, there is enough new stuff here to require a copyright 
> assignment I'm afraid. I would say to read the FAQ but I see it's broken 
> after the system move :-|. But you should look at 
> http://sources.redhat.com/ecos/assign.html anyway.
> 
> Let me know if you have any questions or problems.
> 
> Ta,
> 
> Jifl
>