From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Diego Novillo <dnovillo@google.com>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Samuel Mi <samuel.miing@gmail.com>,
binutils@sourceware.org, gcc <gcc@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Automated Toolchain Building and Testing
Date: Fri, 30 Aug 2013 08:54:00 -0000 [thread overview]
Message-ID: <20130829130251.GI29134@lug-owl.de> (raw)
In-Reply-To: <CAD_=9DQtDpqwUcKyxYUatkBCVxB4r=5aDNGuBMAS--LTjpeHeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
On Thu, 2013-08-29 07:21:28 -0400, Diego Novillo <dnovillo@google.com> wrote:
> On Thu, Aug 29, 2013 at 6:02 AM, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > On Thu, 2013-08-29 10:34:40 +0200, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
> > > I honestly wouldn't worry about such legacy systems: their respective
> > > maintainers take care of testing them, and it would be hard nowadays to
> > > even find both hardware and OS media to set up a new system.
> >
> > Well, I do.
>
> That's fine, but I don't think we should not hold a good solution in
> the quest for the perfect one. How about we start with this version?
> Whoever is interested in extending it to other systems, can do it
> incrementally.
It's already running :) This thread is already about the next
version. The current variant will easily run on anything that is able
to run GIT (probably any other SCM) and SSH (and it'd be easy to adopt
it to anything else like telnet or rlogin.)
> I have not yet caught up to the whole thread, but I suppose the
> possibility of running it on the Compile Farm has been discussed?
David Edelsohn already pointed me to that and I requested an accound
some time ago, but I'm still waiting for a reply. (Though it's holiday
time, so I guess the people doing account maintenance are just out for
a trip.)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: Gib Dein Bestes. Dann übertriff Dich selbst!
the second :
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-08-29 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 10:03 Jan-Benedict Glaw
2013-08-28 10:39 ` Sebastian Huber
2013-08-28 21:26 ` Samuel Mi
2013-08-29 0:52 ` Jan-Benedict Glaw
2013-08-29 1:18 ` Samuel Mi
2013-08-29 7:23 ` Jan-Benedict Glaw
2013-08-29 10:02 ` Samuel Mi
2013-08-29 10:11 ` Dan Kegel
2013-08-29 10:23 ` Paul_Koning
2013-08-29 11:21 ` Jan-Benedict Glaw
2013-08-29 13:02 ` Rainer Orth
2013-08-29 14:33 ` Jan-Benedict Glaw
2013-08-29 22:40 ` Diego Novillo
2013-08-30 8:54 ` Jan-Benedict Glaw [this message]
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=20130829130251.GI29134@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=binutils@sourceware.org \
--cc=dje.gcc@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=samuel.miing@gmail.com \
/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).