[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Arch Roadmap Draft (the anticipated part 3)

From: John Meinel
Subject: Re: [Gnu-arch-users] Arch Roadmap Draft (the anticipated part 3)
Date: Tue, 06 Jul 2004 10:38:31 -0500
User-agent: Mozilla Thunderbird 0.7 (Windows/20040616)

Hash: SHA1

Peter Conrad wrote:

| Hi,
| On Mon, Jul 05, 2004 at 09:33:32PM -0400, James Blackwell wrote:
|>1. if necessary, register the submitted archive
|>2. get the stated changeset
|>2. generate a diff report from the changeset
|>3. record the patchlogs
|>4. get the development head (ex. address@hidden/tla--devo)
|>5. apply the changeset against the development head
|>6. attempt to compile the now modified dev. head and record results
|>7. perform make test and record results
| steps 6 and 7, when run automated and unattended, will allow the execution
| of arbitrary code on the "merge tracker" machine. IMO patches *must* be
| reviewed by a human before they're compiled.
| Bye,
|       Peter

Well, if you validate your submissions first, meaning you only allow
people with a proper gpg signature or that sort of thing, then it
shouldn't be as much of a problem.

It also might be possible to run "make test" in a chroot environment. Is
there any reason why everything after "apply the changeset" couldn't be
walled off from the rest of the world?

But I agree, you probably should do something about it. But it would be
really nice to have it as automated as possible so you can know what's
going to happen when you want to merge.

Also, I think this is comparing to the CVS model, where anyone checks in
anything anyway, and then when a developer comes along to "make test" it
could hose all of their systems.


Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird -


reply via email to

[Prev in Thread] Current Thread [Next in Thread]