octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird NEWS on the OF website


From: Carnë Draug
Subject: Re: Weird NEWS on the OF website
Date: Fri, 15 Jul 2016 21:21:39 +0100

It's not On 15 July 2016 at 06:13, Julien Bect
<address@hidden> wrote:
> Le 14/07/2016 à 17:57, Carnë Draug a écrit :
>>
>> Here's the existing code that handles the news if anyone is interested:
>>
>>      ## piece of text in the NEWS file that marks were to insert news
>>      news_start_token='<!--New news go here-->'
>>      news_final_token='<!--News end here-->'
>>
>>      date=$(date "+%B %d, %Y")
>>
>> replacement="$news_start_token\n<dt>$date<\/dt>\n<dd>\n<p>$name-$version
>> released<\/p>\n<\/dd>"
>>
>>      sed -i.bak "s/$news_start_token/$replacement/" "./NEWS.html"
>>      sed -i.bak "s/$news_start_token/$replacement/" "./index.html"
>>      cp "./index.html" "./index.html.bak"
>>      tac "./index.html.bak" | sed
>> "/$news_final_token/,/<\/dt>/c\\$news_final_token" | tac >
>> "./index.html"
>>
>> The best fix I think would be to after a release, extract the top X
>> entries of the news archive into a separate file, and then have
>> index.html display that.  If anyone is interested in fix it, please
>> do so.
>
>
> Carnë,
>
> Where can I find a description of the entire release process (which scripts
> you run, in which order, etc.) ?
>
> @++
> Julien
>

I have attached the script. The code you wrote would require Octave on the
server.  I'm sure there must be a way to have that done on my side but if I'm
changing this, there must be a way to avoid the duplication of info in the
first place.

Carnë

Attachment: release_OF_to_SF
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]