This is the mail archive of the mauve-patches@sourceware.org mailing list for the Mauve 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: builder StdBuild clean after install

From: Tom Tromey <tromey at redhat dot com>
To: Mark Wielaard <mark at klomp dot org>
Cc: Andrew John Hughes <a dot hughes at dcs dot shef dot ac dot uk>, mauve-patches at sources dot redhat dot com, cpdev at builder dot classpath dot berkeleysignal dot com, abalkiss at redhat dot com, Andrew Hughes <gnu_andrew at member dot fsf dot org>
Date: 05 Jul 2006 11:13:18 -0600
Subject: Re: builder StdBuild clean after install
References: <1152058133.22121.14.camel@elsschot.wildebeest.org> <3F0B9512-2C46-44E4-A1E1-E07489360CD8@dcs.shef.ac.uk> <1152094215.2577.32.camel@elsschot.wildebeest.org> <E22192F9-11BF-4CA6-92CC-F2D5C645EB52@dcs.shef.ac.uk> <1152118673.6853.13.camel@elsschot.wildebeest.org>
Reply-to: tromey at redhat dot com

Mark> We can probably make the scripts directory on builder
Mark> a direct anonymous checkout of mauve cvs and trust that the changes in
Mark> the mauve repository are good.

Yes, I think this is the best plan.  In particular I don't want people
to be checking things to the builder module as 'cpdev' -- it is better
to have a little accountability so we can ask folks to fix up problems
they introduce.

Tom

References:
- builder StdBuild clean after install
  - From: Mark Wielaard
- Re: builder StdBuild clean after install
  - From: Andrew John Hughes
- Re: builder StdBuild clean after install
  - From: Mark Wielaard
- Re: builder StdBuild clean after install
  - From: Andrew John Hughes
- Re: builder StdBuild clean after install
  - From: Mark Wielaard

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