From: Florian Weimer <fw@deneb.enyo.de>
To: gcc@gcc.gnu.org
Subject: Re: source mgt....[_HAS_ gcc relevance]
Date: Mon, 16 Dec 2002 16:36:00 -0000 [thread overview]
Message-ID: <87n0n5wldh.fsf@deneb.enyo.de> (raw)
In-Reply-To: <200212161105.DAA06401@emf.net> (Tom Lord's message of "Mon, 16 Dec 2002 03:05:51 -0800 (PST)")
Tom Lord <lord@emf.net> writes:
> A lot of the thinking behind arch is to scale up and simplify adopting
> practices such as you describe so that they are applied by default to
> pretty much all of the free software (and "open source") projects in
> the world. With your 35, you have social pressures and the power of
> the employer to enforce restrictions like "run the tests before
> committing to mainline" -- but wouldn't it be nice if that were
> automated: so a developer could hit the "try to test and merge" button
> before going home for the night, coming back in the morning to either
> a commit email or a list of test failures -- and if you _didn't_ have
> to write all your own tools for that automation because they were just
> there already, such that setting up a new project with these
> properties was as easy as creating a project on Savannah currently is
> (or, easier :).
Well, you can do this using Aegis for a couple of years now, but I
don't see that Aegis is adopted by the free software crowd. Most of
its members seem to have strong reservations regarding processes which
are enforced by software. ;-)
next prev parent reply other threads:[~2002-12-17 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 3:05 Robert Dewar
2002-12-16 4:15 ` Tom Lord
2002-12-16 4:40 ` Tom Lord
2002-12-16 16:36 ` Florian Weimer [this message]
2002-12-17 0:38 ` Momchil Velikov
2002-12-17 11:41 ` Daniel Egger
2002-12-17 13:17 ` Tom Lord
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 11:03 Robert Dewar
2002-12-16 4:56 Richard Kenner
2002-12-16 5:33 ` Tom Lord
2002-12-14 21:34 source mgt. requirements solicitation Linus Torvalds
2002-12-14 23:12 ` source mgt....[_HAS_ gcc relevance] Tom Lord
2002-12-14 22:12 ` Linus Torvalds
2002-12-15 3:04 ` Zack Weinberg
2002-12-15 3:23 ` Tom Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87n0n5wldh.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).