#8705: Indentation problem in topics/db/models.txt
----------------------------------------------------------+-----------------
          Reporter:  Horst Gutmann <[EMAIL PROTECTED]>  |         Owner:  
nobody          
            Status:  new                                  |     Milestone:  1.0 
            
         Component:  Documentation                        |       Version:  SVN 
            
        Resolution:                                       |      Keywords:  
rst, indentation
             Stage:  Accepted                             |     Has_patch:  1   
            
        Needs_docs:  0                                    |   Needs_tests:  0   
            
Needs_better_patch:  0                                    |  
----------------------------------------------------------+-----------------
Changes (by richardb):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 1.0

Comment:

 Tried out the patch, works as intended and fixes the incorrect rendering
 in the documentation.

 To the original submitter: in future, can you submit patches in {{{svn
 diff}}} format rather than using the diff output from another Version
 Control tool? It will then conform to the
 [http://docs.djangoproject.com/en/dev/internals/contributing/#patch-style
 Django patch guidelines] and make life a lot easier for people (like
 myself) who are using the standard tools :-)

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8705#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to