Minor text updates

This commit is contained in:
Mukund Sivaraman 2010-01-24 11:17:20 +05:30
parent d9d66e6280
commit 2447e38618

15
README
View File

@ -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 repository to 'tinyproxy-developers-list'. Please include a description
of what your patch does. of what your patch does.
Tinyproxy's source code is maintained in a Git repository at Tinyproxy's source code is maintained in a Git repository. The following
<git://www.banu.com/tinyproxy.git>. The following command creates a command creates a local copy of it:
local copy:
---- ----
git clone git://www.banu.com/tinyproxy.git git clone git://www.banu.com/tinyproxy.git
---- ----
The easiest and preferred way to create a patch for submission is to 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 check in your changes locally against the 'master' branch and use `git
mbox-style patch file that contains the diff along with the commit format-patch` to generate a mbox-style patch file that contains the diff
message and author information. Such a formatted patch file can be along with the commit message and author information. Such a formatted
integrated into the upstream repository, automatically keeping the patch file can be integrated into the upstream repository, automatically
commit message and author information. keeping the commit message and author information.
You can also meet developers and discuss development issues and patches You can also meet developers and discuss development issues and patches
in the `#tinyproxy` IRC channel on Freenode (`irc.freenode.net`). in the `#tinyproxy` IRC channel on Freenode (`irc.freenode.net`).