#10424: Expand matrix augment'ing to allow vectors as input
-----------------------------------+----------------------------------------
   Reporter:  rbeezer              |       Owner:  jason, was     
       Type:  enhancement          |      Status:  positive_review
   Priority:  minor                |   Milestone:  sage-4.6.2     
  Component:  linear algebra       |    Keywords:                 
     Author:  Rob Beezer           |    Upstream:  N/A            
   Reviewer:  Joris Vankerschaver  |      Merged:                 
Work_issues:                       |  
-----------------------------------+----------------------------------------

Comment(by robertwb):

 Replying to [comment:20 jdemeyer]:
 > Replying to [comment:19 jason]:
 > > I would *love* if the release manager's script would just
 automatically put the ticket number on, as a standard part of importing a
 patch.  If this was accepted practice, it would cut down on yet one more
 administrative annoyance which has room for human error in posting a
 patch.  Not to mention that it would then make the format consistent,
 which means tools could more easily search/filter/do stuff with the hg
 commit messages.
 >
 > That would be easy to implement, but then we would need people to
 suddenly '''not''' put ticket numbers themselves in the commit message.

 Why? Wouldn't it be easier to have a script that prepends the ticket
 number if it isn't already in the description?

 > The best solution would be to add another "header" field, so the top of
 a patch file would look like
 > {{{
 > # HG changeset patch
 > # User Rob Beezer <[email protected]>
 > # Date 1291401373 28800
 > # Node ID f1dfd7d6d7fcea5f8473979c4052824b2a8579f1
 > # Parent  f843fff860efc5c791da4d8f7d85d434ba057de9
 > # Ticket 10242
 > 10424: augmentation of matrix augment method
 > }}}
 >
 > But can hg cope with this and can we grep for it?

 I don't know, but it wouldn't show up in the shortlogs, so better to have
 it in the first line of the description.

 In any case, there should be IMHO a different setting than "needs work"
 for trivial issues like this.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10424#comment:21>
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