This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: coalesced repies


On Mon, 9 Dec 2002, Tom Lord wrote:

> In other words, where Diego's pagse talk about two branches, I think
> they should talk about _every_ branch, including those owned by people
> without write access to the main repository.  And if Zach or Mark
> wants to set up a temporary branch for convenience, while merging
> things for the next release milestone -- it should be pretty trivial
> to add pages for that branch.

Doing anything automatically with too many branches on a central system
hits (a) lack of CPU cycles and (b) security, if the branches are from
random untrusted repositories.  The same security problem applies to any
automated test-before-checkin system as has been proposed from time to
time.

If a lot more testing CPU cycles were available, I'd think adding a wider
variety of frequent testing for the mainline and release branches (e.g.  
daily bulk builds of BSD packages/ports and whole GNU/Linux distributions)  
would be of greater value than doing less testing on more miscellaneous
branches.  (However, such bulk builds do need more manual effort to
interpret the results, where failures may well result from bugs in the
packages compiled.)

-- 
Joseph S. Myers
jsm28@cam.ac.uk


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