This is the mail archive of the frysk@sourceware.org mailing list for the frysk 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: meeting

From: Tom Tromey <tromey at redhat dot com>
To: Elena Zannoni <elena dot zannoni at oracle dot com>
Cc: Phil Muldoon <pmuldoon at redhat dot com>, Frysk List <frysk at sourceware dot org>, Project Archer <archer at sourceware dot org>
Date: Fri, 25 Jul 2008 10:31:55 -0600
Subject: Re: meeting
References: <m3zlo9obts.fsf@fleche.redhat.com> <m363qwnz9p.fsf@fleche.redhat.com> <48879E2E.5040200@redhat.com> <4889CF65.1090307@oracle.com>
Reply-to: Tom Tromey <tromey at redhat dot com>

[ CCing archer list ]

Elena> 1. how come not just a simple branch of gdb? It would seem the
Elena> simplest alternative for doing merges?

CVS is a pain to work with.

Elena> 2. I think a wise idea would be to settle on a set of host/targets
Elena> combinations that should always work on
Elena> archer. Ie those should be tested before doing a check in.

Perhaps we can solve it after the fact by running auto-builders and
asking people to fix any regressions they inadvertently introduce.

Or maybe we could try to have some kind of multi-machine patch testing
queue.

I would like to avoid having a lot of individual overhead on each
patch; many patches will be architecture-neutral.  So, automation at
some point in the process is important.

Tom

References:
- meeting
  - From: Tom Tromey
- Re: meeting
  - From: Tom Tromey
- Re: meeting
  - From: Phil Muldoon
- Re: meeting
  - From: Elena Zannoni

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