From owner-freebsd-doc@FreeBSD.ORG  Fri Feb 28 13:30:08 2014
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EE97C4ED
 for <freebsd-doc@freebsd.org>; Fri, 28 Feb 2014 13:30:08 +0000 (UTC)
Received: from mxf1.bahnhof.se (mxf1.bahnhof.se [213.80.101.25])
 by mx1.freebsd.org (Postfix) with ESMTP id A504E1AF1
 for <freebsd-doc@freebsd.org>; Fri, 28 Feb 2014 13:30:08 +0000 (UTC)
Received: from localhost (mxf1.local [127.0.0.1])
 by mxf1-reinject (Postfix) with ESMTP id 6E87D32C19E;
 Fri, 28 Feb 2014 14:30:01 +0100 (CET)
X-Virus-Scanned: by amavisd-new using ClamAV at bahnhof.se (MXF1)
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-99 required=5
 tests=[SPF_PASS=-0.001]
Received: from mxf1.bahnhof.se ([127.0.0.1])
 by localhost (mxf1.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Txz7TiB8CGCG; Fri, 28 Feb 2014 14:29:57 +0100 (CET)
Received: from mail.bjuv.org (h-84-63.a175.priv.bahnhof.se [79.136.84.63])
 by mxf1.bahnhof.se (Postfix) with ESMTP id F3E0332C1A2;
 Fri, 28 Feb 2014 14:29:56 +0100 (CET)
Received: from [192.168.0.2] (elektra.nixnet.jke [192.168.0.2])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.bjuv.org (Postfix) with ESMTPSA id AE7621FFAB;
 Fri, 28 Feb 2014 14:29:56 +0100 (CET)
Message-ID: <53108F54.1070304@cyberinfo.se>
Date: Fri, 28 Feb 2014 14:29:56 +0100
From: Jack-Benny Persson <jack-benny@cyberinfo.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Warren Block <wblock@wonkity.com>
Subject: Re: Correct way of sending patches?
References: <53103D13.9030402@cyberinfo.se>
 <alpine.BSF.2.00.1402280600350.3946@wonkity.com>
In-Reply-To: <alpine.BSF.2.00.1402280600350.3946@wonkity.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-doc@freebsd.org
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2014 13:30:09 -0000

>> Hi,
>>
>> I'm just wondering what the correct way is to send updates and patches
>> to the FreeBSD Handbook? I've read (and heard) of both sending them to
>> this list as well as using send-pr. I was recommended to send them here
>> to the list so I've sent a small patch to the jail chapter. But maybe
>> this wasn't the correct procedure?
> 
> A PR is better because it is kept in a database and not as easily lost
> or forgotten.
> 
> Tangentially, the web version of send-pr is easier to use:
> http://www.freebsd.org/send-pr.html
> 
> Just remember to add a .txt extension to patch filenames
> ("patch.diff.txt") so the web form will accept them.
> 
> Thanks!

Thanks for your kind reply and tip about the .txt extension!
I'll post my updated patch with the web version of send-pr.

Cheers!