diff options
| author | Mukund Sivaraman <muks@banu.com> | 2010-01-24 11:17:20 +0530 |
|---|---|---|
| committer | Mukund Sivaraman <muks@banu.com> | 2010-01-24 11:17:20 +0530 |
| commit | 2447e38618f49a043d28611ef315f44ea56b8899 (patch) | |
| tree | fe789921c3c14237ec4c40e7a60a0e429252f87b | |
| parent | d9d66e6280a497b4c2fec654ef16d95595ae08ad (diff) | |
| download | tinyproxy-2447e38618f49a043d28611ef315f44ea56b8899.tar.gz tinyproxy-2447e38618f49a043d28611ef315f44ea56b8899.zip | |
Minor text updates
| -rw-r--r-- | README | 15 |
1 files changed, 7 insertions, 8 deletions
@@ -87,20 +87,19 @@ 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 source code is maintained in a Git repository at -<git://www.banu.com/tinyproxy.git>. The following command creates a -local copy: +Tinyproxy's source code is maintained in a Git repository. The following +command creates a local copy of it: ---- 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 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. +check in your changes locally against the 'master' branch and use `git +format-patch` to generate a 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. You can also meet developers and discuss development issues and patches in the `#tinyproxy` IRC channel on Freenode (`irc.freenode.net`). |