[pca] pca html report

[Asif Iqbal]

On Mon, Oct 17, 2011 at 5:48 AM, Martin Paul <martin at par.univie.ac.at> wrote:
> Asif Iqbal wrote:
>>
>> Thanks for the patch. I actually would prefer a variable instead of
>> hard coding  wesunsolve.net, like the the original $o{patchurl} or
>> $o{ohost}
>
> The problem is that you probably want different formats when using "pca
> --readme" (in a terminal pure text is preferred) and in the README links in
> HTML output (this can be HTML with extra links etc. as provided by
> wesunsolve). So simply adding a new "readmeurl" option won't be enough. And
> adding two different options to define README locations would be pretty
> confusing.
>
>> ... so I rather have this line be like this
>>
>> printf "<td><a href=\"https://$o{ohost}/readme/README.$id-$crev\">%s</a>
>> (<a href=\"http://wesunsolve.net/readme/id/$id-$crev\">more</a>)</tr>\n",
>> $synopsis;
>
> But where's the added value then? The "http://wesunsolve.net/readme/" link

Yeah you are right, for readme it does not make sense much.

> provides the plain patch README in text format, exactly the same as the
> "https://$o{ohost}/readme/" link. I don't see a big advantage here,
> especially as access to the READMEs on Oracle's server is pretty stable and
> fast.
>
> Martin.
>
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?