db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html
Date Fri, 14 Jun 2013 07:20:20 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683158#comment-13683158

Knut Anders Hatlen commented on DERBY-6257:

Hi Bryan,

I'm not sure if I've updated the website after the changes, but my understanding of the process
is as following:

1) Both files should be modified. Or, more precisely, you modify the file under src/ and run
forrest which modifies the file under build/ for you.

2) In the discussion on the PMC list during the website migration, it looks like those who
made changes used two separate commits. That is, first commit in the top-level directory and
then cd into the build/site directory and repeat svn commit. It was also suggested that a
single commit should work, like this:

    svn commit -m "commit message" . build/site

I didn't see anyone actually trying that command and verifying that it worked, though.

3) I cannot imagine the order of the two commits has any significance.
> Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html
> ---------------------------------------------------------------------------------------
>                 Key: DERBY-6257
>                 URL: https://issues.apache.org/jira/browse/DERBY-6257
>             Project: Derby
>          Issue Type: Bug
>          Components: Web Site
>            Reporter: Bryan Pendleton
>            Assignee: Bryan Pendleton
>            Priority: Trivial
>         Attachments: docs.diff
> The Subversion home page has moved. The new home page is http://subversion.apache.org/
We should fix the link on http://db.apache.org/derby/dev/derby_source.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message