From 2447e38618f49a043d28611ef315f44ea56b8899 Mon Sep 17 00:00:00 2001 From: Mukund Sivaraman Date: Sun, 24 Jan 2010 11:17:20 +0530 Subject: Minor text updates --- README | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'README') diff --git a/README b/README index a813136..b9a46ba 100644 --- a/README +++ b/README @@ -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 -. 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`). -- cgit v1.2.3