#8680: untabify Sage again, and make it stick
-----------------------------+----------------------------------------------
Reporter: jhpalmieri | Owner: jason
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.4
Component: misc | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by jason):
Replying to [comment:4 mvngu]:
> I'm in favour of automating as much as possible tedious tasks such as
the above. An advantage is that prior to reviewing a patch, a reviewer (or
indeed a continuous integration system) could run a patch through this
sanity checker script. If all rules in the script pass, then the reviewer
could then proceed with reviewing the implementation contained in the
patch.
> [[BR]][[BR]]
In this spirit, I'm strongly in favor of the sage -merge script prepending
the ticket number where a patch came from, thus fulfilling the requirement
that the ticket number be in the patch. This way (1) the ticket number is
guaranteed to be accurate and consistently done (i.e., reflects what
ticket you can find the patch at, and always is #xxxx: <commit>), and (2)
it doesn't waste developer's time to look up and type in correctly a 4-5
digit number which could be totally automated.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8680#comment:5>
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.
