diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2007-09-09 22:10:47 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2007-09-09 22:10:47 +0000 |
| commit | 5e19019bcac39421adf6e0ee8cc3b3fd2cc1ff08 (patch) | |
| tree | a00c1640b2b3b33e4f86206d4d1613b9120d07bc /docs | |
| parent | 84f618249402e8fd5673efbe2604e2b3f17b35a0 (diff) | |
Added bullet to docs/contributing.txt about creating diffs from the top-level trunk directory
git-svn-id: http://code.djangoproject.com/svn/django/trunk@6078 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/contributing.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/contributing.txt b/docs/contributing.txt index b0df62fe99..f1ad0e3bb0 100644 --- a/docs/contributing.txt +++ b/docs/contributing.txt @@ -122,6 +122,11 @@ Patch style English than in code. Indentation is the most common example; it's hard to read patches when the only difference in code is that it's indented. + * When creating patches, always run ``svn diff`` from the top-level + ``trunk`` directory -- i.e., the one that contains ``django``, ``docs``, + ``tests``, ``AUTHORS``, etc. This makes it easy for other people to apply + your patches. + * Attach patches to a ticket in the `ticket tracker`_, using the "attach file" button. Please *don't* put the patch in the ticket description or comment unless it's a single line patch. |