This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Possible deadlock in serial.c

From: Roland Caßebohm <roland dot cassebohm at visionsystems dot de>
To: Gary Thomas <gary at mlbassoc dot com>, "David Marqvar (DAM)" <DAM at tt dot dk>
Cc: eCos patches <ecos-patches at sources dot redhat dot com>
Date: Thu, 22 May 2003 10:45:43 +0200
Subject: Re: Possible deadlock in serial.c
References: <E70B4FA554FB6C44BC7FAC9A9CE0CBC436D53D@ntex.tt.dk> <1053544735.1558.1019.camel@hermes>

On Mittwoch, 21. Mai 2003 21:18, Gary Thomas wrote:
> I keep my own CVS tree for local development.  I merge the public
> sources to it as they change.  When I need to start a new project,
> I base it on my local repository which I can tag, etc.  That way
> I can reliably develop and deliver code, no matter what the public
> tree does.  Of course, whenever possible my local changes are pushed
> out to the public tree as well.

Hi,

this is very interesting for me, how do you do that? 
How can I merge public sources to my local tree and how can I make
diffs from my local tree against the public?

Many thanks,

Roland

Follow-Ups:
- Tracking eCos source in CVS (was: Possible deadlock in serial.c)
  - From: Daniel Néri

References:
- RE: Possible deadlock in serial.c
  - From: David Marqvar (DAM)
- RE: Possible deadlock in serial.c
  - From: Gary Thomas

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]