From d9d66e6280a497b4c2fec654ef16d95595ae08ad Mon Sep 17 00:00:00 2001 From: Mukund Sivaraman Date: Sun, 24 Jan 2010 11:07:28 +0530 Subject: Minor text updates to the patch section --- README | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'README') diff --git a/README b/README index bffa98e..a813136 100644 --- a/README +++ b/README @@ -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 . The -following command creates a local copy: +Tinyproxy's source code is maintained in a Git repository at +. 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. -- cgit v1.2.3