public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: gene.heskett@verizon.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@linux.ie>,
	Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [RFC/patch] macro_removal_agp_mtrr.diff
Date: Sat, 04 Sep 2004 17:33:09 +0100	[thread overview]
Message-ID: <1094315580.10555.23.camel@localhost.localdomain> (raw)
In-Reply-To: <200409041147.35522.gene.heskett@verizon.net>

On Sad, 2004-09-04 at 16:47, Gene Heskett wrote:
> Unforch, it appears not to be available as a tarball, or group of 
> tarballs stuffed in a "grab all these" directory.  While I probably

Look harder. Its a single tarball.

> wouldn't be anything but a src of distracting questions, I still 
> wouldn't mind an opportunity to build and test (and report on the 
> grins and scowls) this if it can be built in a sandbox, leaving the 
> existing X.org-6.7 release intact for rescue recovery.  I have the 
> disk space, and plenty of cpu cycles I can steal from setiathome, so 
> thats not a major problem.

Sandbox build _should_ work now. There were problems there at one point.
Or there are vendor rpms available of the testing packages for the
brave.


  reply	other threads:[~2004-09-04 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04 10:02 [RFC/patch] macro_removal_agp_mtrr.diff Dave Airlie
2004-09-04 10:11 ` Christoph Hellwig
2004-09-04 10:14 ` Arjan van de Ven
2004-09-04 10:21   ` Dave Airlie
2004-09-04 10:30   ` Dave Airlie
2004-09-04 10:36     ` Arjan van de Ven
2004-09-04 10:37     ` Arjan van de Ven
2004-09-04 13:23       ` Dave Airlie
2004-09-04 13:30         ` Arjan van de Ven
2004-09-04 15:47         ` Gene Heskett
2004-09-04 16:33           ` Alan Cox [this message]
2004-09-04 22:04             ` Lee Revell

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=1094315580.10555.23.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=airlied@linux.ie \
    --cc=arjanv@redhat.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.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