[asterisk-bugs] [JIRA] (ASTERISK-20703) Merge menuselect into the Asterisk source

[Jason Parker (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201862#comment-201862 ] 

Jason Parker edited comment on ASTERISK-20703 at 1/18/13 2:33 PM:
------------------------------------------------------------------

{noformat}$ svn up -r9138
Updating '.':
Skipped 'drivers/dahdi/oct612x' -- An obstructing working copy was found
 U   drivers/dahdi
Removed external 'drivers/dahdi/oct612x'
Updated to revision 9138.
Summary of conflicts:
  Skipped paths: 1{noformat}
                
      was (Author: jparker):
    $ svn up -r9138
Updating '.':
Skipped 'drivers/dahdi/oct612x' -- An obstructing working copy was found
 U   drivers/dahdi
Removed external 'drivers/dahdi/oct612x'
Updated to revision 9138.
Summary of conflicts:
  Skipped paths: 1
                  
> Merge menuselect into the Asterisk source
> -----------------------------------------
>
>                 Key: ASTERISK-20703
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20703
>             Project: Asterisk
>          Issue Type: Improvement
>          Components: General
>            Reporter: Matt Jordan
>
> So this ought to be fun.
> While discussing the migration process from subversion to git that we'd like to do for the Asterisk project, the issue of menuselect came up.  Namely, that it makes the migration to git a *lot* harder.
> Since Asterisk is the only project that uses menuselect, it can be moved into the Asterisk project.  There are a lot of implications to this however, including changes to the repotools project's scripts.  We'll have to also make sure that updating to a version of Asterisk is relatively smooth, as this will have to occur in all of the major version branches.
> This will also impact older versions of Asterisk, so the menuselect repo will still have to exist to support versions prior to Asterisk 1.8.

--
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