#8712: Use `optparse` in sage -merge for increased usability.
---------------------------+------------------------------------------------
   Reporter:  timdumol     |       Owner:  GeorgSWeber 
       Type:  enhancement  |      Status:  needs_review
   Priority:  major        |   Milestone:  sage-4.4    
  Component:  build        |    Keywords:              
     Author:  Tim Dumol    |    Upstream:  N/A         
   Reviewer:               |      Merged:              
Work_issues:               |  
---------------------------+------------------------------------------------

Comment(by timdumol):

 The help message reads:

 {{{
 Usage: sage -merge [options] [ticket-number]

 Tries to automate the process of merging tickets in release management.
 See http://wiki.sagemath.org/devel/ReleaseManagement for more info.

 Example usage:

 sage -merge -c or sage -merge --candidates

     * List all candidates for merging, i.e. all trac tickets with positive
 review.

 sage -merge <ticket_number> <options>

     * Download patches from trac for the given ticket number, merge them,
 run tests, and report the results.

 sage -merge -a <options> or sage -merge --all <options>

     * For each ticket on trac with a positive review, download the
 patches, apply them, and run doctests. At the end, report which tickets
 passed, which failed, and which didn't have any files to doctest (as is
 commonly the case with tickets for new spkg's).


 Options:
   -h, --help            show this help message and exit
   -a, --all             For each ticket on trac with a positive review,
                         download, apply, and test each. At the end, report
                         which pass, fail, and have no files to doctest
   -c, --candidates      List all candidates for merging, i.e., all trac
                         tickets with positive review
   -v, --verbose         Display the results of each test
   -n NUM_THREADS, --num-threads=NUM_THREADS
                         Number of threads to work with
   -r REPOSITORY, --repository=REPOSITORY
                         Which repository to apply to. Choices: ['bin',
                         'extcode', 'sage', 'examples', 'scripts', 'main']
   -t TEST, --test=TEST  What things to doctest. Choices: ['none', 'files',
                         'directory', 'long'] or any prefix of a choice.
   -o, --overwrite       Whether to overwrite files when downloading.
   -d DIRECTORY, --directory=DIRECTORY
                         Directory to store patches in.

   Behavior:
     Behavior after merging. Default is to pop after merging

     -l, --leave-in-queue
                         Leaves the patches in mercurial queue. Conflicts
 with
                         --finish.
     -f, --finish        Performs qfinish, commiting the patches. Conflicts
                         with --leave-in-queue.
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8712#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to