public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Setting execute permission on SSI files
Date: Mon, 30 Mar 2009 14:25:00 -0000	[thread overview]
Message-ID: <49D0D643.3070301@jifvik.org> (raw)
In-Reply-To: <49CFC28E.7040801@dallaway.org.uk>

John Dallaway wrote:
> Hi Jifl
> 
> John Dallaway wrote:
> 
> 
>>I added a couple of boards to the eCos board database but didn't set
>>execute permissions on the .html files before I added them. Apache will
>>therefore not process these files as SSI files.
>>
>>I can find no way to change the execute permissions on a file from a CVS
>>client once it has been added to the repository. Removing and adding
>>again with the correct permissions does not help. Can you set the
>>executable bits on the following files manually for me please?
>>
>>
>>>boards/inc/m5272c3.html
>>>boards/inc/stm3210e_eval.html
> 
> 
> I added new files boards/inc/m5272c3_.html and
> boards/inc/stm3210e_eval_.html to workaround this issue for now.

I've fixed it.

NB I am missing a lot of ecos-related mail as my ISP was having 
unexplained problems talking to sourceware.org. It's temporarily fixed, 
and may or may not be permanently fixed. Either way there's a lot of mail 
I won't know about, FYI. Not that it made much difference given my 
non-existent ecos bandwidth recently :-/.

Jifl
-- 
------["The best things in life aren't things."]------      Opinions==mine

      reply	other threads:[~2009-03-30 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 10:40 John Dallaway
2009-03-29 18:49 ` John Dallaway
2009-03-30 14:25   ` Jonathan Larmour [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=49D0D643.3070301@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).