#3761: [with patch; needs work] warning when run sage binary if the processor
instruction set doesn't support everything that was on the machine where
sage was built
---------------------+------------------------------------------------------
 Reporter:  was      |        Owner:  cwitty  
     Type:  defect   |       Status:  new     
 Priority:  blocker  |    Milestone:  sage-3.2
Component:  misc     |   Resolution:          
 Keywords:           |  
---------------------+------------------------------------------------------
Comment (by mvngu):

 For the patch '''scripts-3761.patch''', here are some possible
 documentation fixes:
 [[BR]][[BR]]
 1.
 {{{
 -moved make sure the location and processor flags files are
 +moved, make sure the location and processor flags files are
 }}}
 So after applying that diff, you'd get this documentation snippet:
 {{{
 """
 Check whether or not this install of Sage moved.  If it hasn't
 moved, make sure the location and processor flags files are
 written.
 """
 }}}
 I know I'm nit-picking, but the second sentence is rather long. Leaving
 out the extra comma won't change what you're trying to say with that
 sentence. But it can take some time for readers (including yours truly) to
 figure out what you're saying. I think the extra comma would make it
 easier to read your documentation.
 [[BR]][[BR]]
 2.
 {{{
 -# On a system without /proc/cpuinfo, so don't bother In
 +# On a system without /proc/cpuinfo, so don't bother. In
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3761#comment:8>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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