diff options
| author | Mukund Sivaraman <muks@banu.com> | 2010-01-24 11:07:28 +0530 |
|---|---|---|
| committer | Mukund Sivaraman <muks@banu.com> | 2010-01-24 11:07:28 +0530 |
| commit | d9d66e6280a497b4c2fec654ef16d95595ae08ad (patch) | |
| tree | a277fcaff4aa854c720952745d8783450aaf9a6a | |
| parent | 70885bf029a6f857684f99618f867b5c47767ae0 (diff) | |
Minor text updates to the patch section
| -rw-r--r-- | README | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -87,8 +87,9 @@ source, please send a patch (preferably as a unified diff. i.e. `diff repository to 'tinyproxy-developers-list'. Please include a description of what your patch does. -Tinyproxy's git repository is <git://www.banu.com/tinyproxy.git>. The -following command creates a local copy: +Tinyproxy's source code is maintained in a Git repository at +<git://www.banu.com/tinyproxy.git>. The following command creates a +local copy: ---- git clone git://www.banu.com/tinyproxy.git @@ -96,8 +97,8 @@ git clone git://www.banu.com/tinyproxy.git The easiest and preferred way to create a patch for submission is to check in your changes locally and use `git format-patch` to generate a -mbox-style commit file that contains the diff along with the commit -message and author information. Such a format-patch file can be +mbox-style patch file that contains the diff along with the commit +message and author information. Such a formatted patch file can be integrated into the upstream repository, automatically keeping the commit message and author information. |