public inbox for [email protected]  

help / color / mirror / Atom feed

From: Heikki Linnakangas <[email protected]>
To: Pg Docs <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Subject: Re: developer FAQ
Date: Tue, 05 Apr 2011 21:48:56 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On 05.04.2011 21:28, Heikki Linnakangas wrote:
> On 05.04.2011 21:13, Alvaro Herrera wrote:
>> Hi,
>>
>> I just noticed that the developer's FAQ has this question with a link to
>> the anoncvs cvsweb:
>> http://wiki.postgresql.org/wiki/Developer_FAQ#How_is_the_source_code_organized.3F
>>
>>
>> The link is
>> http://anoncvs.postgresql.org/cvsweb.cgi/~checkout~/pgsql/src/tools/backend/index.html
>>
>> which no longer works.
>>
>> The equivalent file in Git seems to be this one:
>> http://git.postgresql.org/gitweb?p=postgresql.git;a=blob;f=src/tools/backend/index.html;hb=HEAD
>>
>>
>> However, this displays the raw HTML instead of having it be interpreted
>> by the browser. Anyone knows how to change this?
>
> Oh, rats. I misunderstood your question, and changed the link to what
> you posted because it seemed to work for me. It was only after I saved
> that I realized what you meant - the link displays the html source, not
> properly rendered html.
>
> Googling around for a solution...

Hmm, is the /etc/mime.types file missing or somehow strange on that 
host? When I do "git instaweb" on my laptop in a clone of the repository 
and navigate to that index.html, it renders fine.

However, none of the links work. They contain relative links like 
"../../backend/bootstrap", which doesn't work with the more complicated 
URL scheme that gitweb uses.

How about we move this page to the wiki? It'd be more likely to get 
updated there too.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: developer FAQ
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox