hi send an email to [email protected]
and confirm the response you receive (as it will ask you to do) rgds jan i On Tue, 28 Mar 2017 at 15:55, Adam Skwersky <[email protected]> wrote: > unsubscribe > > ----------------------- > Adam Skwersky > Senior Software Engineer > ClearQuest Development > HCL Technologies Ltd. > (508) 882-7683 > Products & Platforms > [email protected] > www.hcltech.com > > Join us at IBM Interconnect 2017 > March 19-23, Las Vegas > > > > -----Original Message----- > From: Henri Yandell (JIRA) [mailto:[email protected]] > Sent: Monday, March 27, 2017 8:03 PM > To: [email protected] > Subject: [jira] [Comment Edited] (ATTIC-165) Procedure update / question > list. > > > [ > https://issues.apache.org/jira/browse/ATTIC-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944268#comment-15944268 > ] > > Henri Yandell edited comment on ATTIC-165 at 3/28/17 12:02 AM: > --------------------------------------------------------------- > > To update the header of websites, I typically: > > 1) Find the website source (or at least the HTML) > 2) Identify the architecture; it's typically either a) template files, or > b) generated HTML. > 2a) If template files, then identify the main template (often called > skeleton it seems) and edit the body tag to include: > {code:xml} > <div style="background: red"><h1>YYYY/MM/DD - Apache XYZ has been > retired. </h1><h2>For more information, please explore the <a href=" > http://attic.apache.org/";>Attic</a>. </h2></div> {code} > > 2b) If generated HTML, then run a search and replace. > > So, firstly see the output of something like: > > {code} > find . -type f | xargs grep '<body' > {code} > > Then I run: > > {code} > find . -type f | xargs grep '<body' | xargs perl -pi -e > 's!(<body[^>]*>)!\1<div style="background: red"><h1>YYYY/MM/DD - Apache XYZ > has been retired. </h1><h2>For more information, please explore the <a > href="http://attic.apache.org/";>Attic</a>. </h2></div>!' > {code} > > > was (Author: bayard): > To update the header of websites, I typically: > > 1) Find the website source (or at least the HTML) > 2) Identify the architecture; it's typically either a) template files, or > b) generated HTML. > 2a) If template files, then identify the main template (often called > skeleton it seems) and edit the body tag to include: > {code:xml} > <div style="background: red"><h1>YYYY/MM/DD - Apache XYZ has been > retired. </h1><h2>For more information, please explore the <a href=" > http://attic.apache.org/";>Attic</a>. </h2></div> {code} > > 2b) If generated HTML, then run a search and replace. > > So, firstly see the output of something like: > > {code} > find . -type f | xargs grep '<body' > {code} > > Then I run: > > {code} > find . -type f | xargs grep '<body' | xargs perl -pi -e > 's!(<body[^>]*>)!\1<div style="background: red"><h1>YYYY/MM/DD - Apache XYZ > has been retired. </h1><h2>For more information, please explore the <a > href="http://attic.apache.org/";>Attic</a>. </h2></div> {code} > > > Procedure update / question list. > > --------------------------------- > > > > Key: ATTIC-165 > > URL: https://issues.apache.org/jira/browse/ATTIC-165 > > Project: Attic > > Issue Type: Improvement > > Reporter: jan iversen > > Priority: Minor > > > > Reading the current procedure http://attic.apache.org/process.html, > leaves some open questions: > > --> Create page on Attic site: > > --> http://attic.apache.org/projects/${project}.html > > Site is in http://svn.apache.org/repos/asf/attic/site > > Add page to xdocs/projects (manually?) How to generate the new site ? > > --> i. Update website with Attic notice: http://${project}.apache.org/ > > Missing pointer to office notice text. > > (Will be updated as I continue with Abdera) > > > > -- > This message was sent by Atlassian JIRA > (v6.3.15#6346) > > > ::DISCLAIMER:: > > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > > ---------------------------------------------------------------------------------------------------------------------------------------------------- > -- Sent from My iPad, sorry for any misspellings.
