public inbox for
 help / color / mirror / Atom feed
From: Jonathan Larmour <>
To: Andrew Lunn <>
Cc: Andrew Lunn <>,
		eCos Maintainers <>
Subject: Re: hardware.html help!
Date: Mon, 20 Feb 2006 01:23:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Andrew Lunn wrote:
> On Sun, Feb 19, 2006 at 10:48:41PM +0100, Andrew Lunn wrote:
>>Hi folks
>>Probably one for Jifl
>>I've broken the "Supported Hardware" page, 
>>There is an obvious cut/paste error in board-tablerow.html
>> <td><!--#if expr="$platurl" --><a href="<!--#echo var="platurl" -->" target="_top"><!--#endif -->
>>  <!--#echo var="plat" --><!--#if expr="$procurl" --></a><!--#endif --></td>
>>the procurl should be platurl. This is causing extra </a> tokens. I
>>"fixed" this error and committed the change and it all went pear
>>shaped. So i reversed the patch but it stayed pear shaped!
>>Any ideas what i have broken?
> I think this is to do with the execute bit having to be set for server
> side includes to work. Could somebody with logon to the server take a
> look at the permissions on the files.

Indeed that's what it was on a number of files, although there was a 
little quoting mistake in boards/inc/at91phycore.html that I fixed too.

Unfortunately I believe you have to set the permissions correctly the 
first time a file is "cvs add"ed, otherwise it can only be fixed with 
local shell access to the CVS repository.

Anyway all sorted, hopefully quickly enough!

eCosCentric    The eCos and RedBoot experts
------["The best things in life aren't things."]------      Opinions==mine

  reply	other threads:[~2006-02-20  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 21:48 Andrew Lunn
2006-02-19 22:16 ` Andrew Lunn
2006-02-20  1:23   ` Jonathan Larmour [this message]
2006-02-20  8:40     ` Andrew Lunn
2006-02-20 13:02       ` Jonathan Larmour

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).