docs/186499: The Porters Handbook - better diff description

[Ondra Knezour]

>Number:         186499
>Category:       docs
>Synopsis:       The Porters Handbook - better diff description
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 05 23:00:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Ondra Knezour
>Release:        
>Organization:
>Environment:
>Description:
In the 4.4 Patching section of the Porters Handbook first sentence reads as "In the preparation of the port, files that have been added or changed can be picked up with a diff(1) for later feeding to patch(1)."

Inexperienced porter who just started trying may not know which diff options should be used (tested on myself) and default output of diff file new_file can not be used because paths of the files are missing. 
>How-To-Repeat:

>Fix:
Someone better in both the english and ports maintaining than me may suggest change describing appropriate diff usage. I, as inexperienced person, would consider useful something like:

Before changing file make copy of it. Later you can produce patch with command 

diff [-some-magic-options-here] file.original file.changed > patch.file

which can be placed to PATCHDIR to be later fed to patch.



>Release-Note:
>Audit-Trail:
>Unformatted: