linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Buell <alex.buell@munted.org.uk>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-fbdev@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Framebuffer HOWTO 1.3 released
Date: Thu, 09 Sep 2010 23:45:37 +0000	[thread overview]
Message-ID: <1284075937.17843.5.camel@lithium> (raw)
In-Reply-To: <20100909155436.2b1bff1f.rdunlap@xenotime.net>

On Thu, 2010-09-09 at 15:54 -0700, Randy Dunlap wrote:
> On Sun, 8 Feb 2009 09:08:44 +0000 Alex Buell wrote:
> 
> > Hi,
> > 
> > I've dug out my original Framebuffer HOWTO sgml document written during
> > the late 1990s, and have updated it with current e-mail address. You
> > can grab it from here:
> > http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html
> 
> Hi Alex,
> 
> cc-ing linux-fbdev@vger.kernel.org for posterity.
> 
> That file (*.html) above is actually a tar.gz file.
> Could you rename it so that tools actually work with it?
> 
> or better yet, could you put the html files on a (or your) server
> for viewing?
> 
> Thanks.

Oh dear. 

The correct URL is
http://www.munted.org.uk/programming/Framebuffer-HOWTO/

There are also three tarballs:
http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html.tar.gz
http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.txt.tar.gz
http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.xml.tar.gz

Hope this is helpful. Sorry about the bad URL that was given out!
-- 
Tactical Nuclear Kittens

      reply	other threads:[~2010-09-09 23:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090208090844.7a27d740@lithium.local.net>
2010-09-09 22:54 ` Framebuffer HOWTO 1.3 released Randy Dunlap
2010-09-09 23:45   ` Alex Buell [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=1284075937.17843.5.camel@lithium \
    --to=alex.buell@munted.org.uk \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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 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 NNTP newsgroup(s).