From: Jared Rhine <jared@wordzoo.com>
To: xen-devel@lists.sourceforge.net
Subject: minor correction to install.sh
Date: Thu, 27 Jan 2005 11:57:31 -0800 [thread overview]
Message-ID: <87mzuuejbo.wl@badger.wordzoo.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12354D@liverpoolst.ad.cl.cam.ac.uk>
[Ian == m+Ian.Pratt@cl.cam.ac.uk on Wed, 26 Jan 2005 20:16:15 -0000]
Ian> In hind sight it was a bad idea to start unravelling the build
Ian> system. It wasn't pretty, but it worked...
I personally think the improvements to the build system were worth the
risk of merging. I do think that fewer non-trivial changes should get
applied to the testing and unstable trees simultaneously and that
large batches of changes applied at the same time always carry risk.
Please don't shy off of build-related improvements in the future; good
building, packaging, and development support has wide-ranging benefits
to the community. Yeah, sometimes you won't anticipate all
environments, but there's always the stable tree for those who don't
feel like helping to catch and report breakages.
-- jared@wordzoo.com
"Tiger gotta hunt. Bird gotta fly.
Man gotta sit and wonder why, why, why.
Tiger gotta sleep. Bird gotta land.
Man gotta tell himself he understand." -- Kurt Vonnegut Jr.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-27 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 20:16 minor correction to install.sh Ian Pratt
2005-01-27 19:57 ` Jared Rhine [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 18:33 Paul Larson
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=87mzuuejbo.wl@badger.wordzoo.com \
--to=jared@wordzoo.com \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.