infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16614) Migration assistance converting geronimo config to gitbox
Date Mon, 18 Jun 2018 17:45:00 GMT

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

Chris Lambertus commented on INFRA-16614:
-----------------------------------------

Sorry this still doesn't make sense to me. Why is the repo called geronimo.git when geronimo
encompasses much more than just the config? What happens when some other part of geromino
wants to break out a separate git repo? It seems to me to make much more sense for the git
repo to be called geronimo-config.git. Can you help me understand why you want to have such
a generalized name for an svn subcomponent?


> Migration assistance converting geronimo config to gitbox
> ---------------------------------------------------------
>
>                 Key: INFRA-16614
>                 URL: https://issues.apache.org/jira/browse/INFRA-16614
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: GitBox, Github
>            Reporter: John D. Ament
>            Priority: Major
>
> Need a little bit of infra help on this.  We would like to convert geronimo config from
svn to git, however to do that we need the mirror reset/deleted which is presently on github.
 It's mirroring our SVN tree https://svn.apache.org/repos/asf/geronimo/components/config/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message