www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-3276) Figure out what to do about website content.
Date Thu, 30 Dec 2010 16:36:46 GMT

    [ https://issues.apache.org/jira/browse/INFRA-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976064#action_12976064
] 

Eric Evans commented on INFRA-3276:
-----------------------------------

I think you could use a branch that contains nothing but the site content and which shares
no history with the others.  See the `gh-pages' branches on Github if you're looking for a
precedent.  There should be a convention for naming these branches too I think (as there is
on Github).

> Figure out what to do about website content.
> --------------------------------------------
>
>                 Key: INFRA-3276
>                 URL: https://issues.apache.org/jira/browse/INFRA-3276
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Paul Joseph Davis
>            Priority: Minor
>
> I haven't seen any discussion on what people are going to expect to happen to directories
outside of trunk, branches, and tags. For instance, what will we end up doing with the site
directories?
> It might be as simple as just creating repos for each one that are $project-site.git
but I figured I'd ask for input.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message