Index: [thread] [date] [subject] [author]
  From: becka@rz.uni-duesseldorf.de
  To  : ggi-develop@eskimo.com
  Date: Fri, 17 Jul 1998 13:28:30 +0200 (MET DST)

Re: triggered some probs with libAA-target

Hi !

> The problem is that you have to define MANSYNC_CHILD
> or MANSYNC_PTHREAD before including ../common/mansync.in,
> and thats not a recents change. It was made several
> months ago by Steve Cheng, and it was clearly announced
> on the mailinglist.
> 
> Maybe we should have a maintainer in charge of every
> target so that they doesn't just get forgotten when changes
> like this is made?

That is _NOT_ how things should work. If you make a change that affects
other code, then either fix that code yourself or get the maintainer to do
it for you.

This is what I was after with the (failed) move towards a diff-oriented 
system. We can't just rely on "someone will fix that".

Look at what Mozilla folks are doing ... They will instantly freeze the
tree, when it does not compile and not move on until it runs again.

So _PLEASE_ do not work with that "someone else will fix it" attitude.
If you break things, fix them afterwards (at best before you commit).

CU,ANdy

P.S.: Steve - this isn't directed at you. It's just my general opinion.

-- 
Andreas Beck              |  Email :  <Andreas.Beck@ggi-project.org>

Index: [thread] [date] [subject] [author]