From owner-svn-ports-head@FreeBSD.ORG Wed Nov 21 15:52:55 2012 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 96EF4E57 for ; Wed, 21 Nov 2012 15:52:55 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 6689A8FC14 for ; Wed, 21 Nov 2012 15:52:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qALFqthZ021463 for ; Wed, 21 Nov 2012 15:52:55 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qALFqt8I021453 for svn-ports-head@freebsd.org; Wed, 21 Nov 2012 15:52:55 GMT (envelope-from bdrewery) Received: (qmail 95779 invoked from network); 21 Nov 2012 09:52:53 -0600 Received: from unknown (HELO ?192.168.0.74?) (freebsd@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 21 Nov 2012 09:52:53 -0600 Message-ID: <50ACF8E8.5080706@FreeBSD.org> Date: Wed, 21 Nov 2012 09:53:12 -0600 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Eygene Ryabinkin Subject: Re: svn commit: r307612 - in head/misc/astrolog: . files References: <201211210949.qAL9nl4a018306@svn.freebsd.org> <50ACB0A7.1030108@freebsd.org> <50ACBE7D.70203@freebsd.org> <20121121120128.GC4474@droso.net> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0DA31DA713E59D992E052D5F" Cc: svn-ports-head@freebsd.org, Andrey Chernov , svn-ports-all@freebsd.org, ports-committers@freebsd.org, Erwin Lansing , Chris Rees X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 15:52:55 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0DA31DA713E59D992E052D5F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/21/2012 8:53 AM, Eygene Ryabinkin wrote: > Wed, Nov 21, 2012 at 01:01:29PM +0100, Erwin Lansing wrote: >> On Wed, Nov 21, 2012 at 03:43:57PM +0400, Andrey Chernov wrote: >>> On 21.11.2012 15:10, Chris Rees wrote: >>> >>> Yes, but the new naming convention is something which should be decid= ed >>> by portmgr@ to keep all things in line. F.e. will it be '-' or '_' or= >>> '=3D' or some combination of them etc? It is unknown to me at this mo= ment, >>> so I prefer to stay the old one I see. >> >> "Please only use characters [-+._a-zA-Z0-9] for naming your patches. D= o >> not use any other characters besides them. Do not name your patches li= ke >> patch-aa or patch-ab etc, always mention the path and file name in pat= ch >> names." >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/slow= -patch.html >> >> Imporovements to the handbook are of course always welcome. >=20 > The per-file patches are always make me sad: you're loosing the > metadata about the grouping of diff hunks into changes and makes the > non-trivial fixes harder to understand, so when I first took > maintainership of OpenOSPFD, I was struggling with the patch files, > because it was very non-trivial to find which patches should be > dropped for the new releases and which should be kept/modified and how > all hunks in all diffs are related to each other. And this makes life > for the new maintainers especially hard: they have no background on > what previous ones were patching and it is sometimes not really easy > to get the idea from the port commit logs, so some time should be > spent on resurrecting this metadata. >=20 > As I understand, the problem with the grouped patches is the order of > their application while the per-file patches has no such problem and > it is the only technical answer to the question "why handbook teaches > us about per-file patches rather than the real commit diffs", but if > we will implement the proper patch ordering (just by doing sort before > patch application), won't it go away? >=20 I agree. Splitting logically-grouped changes out into multiple patches is confusing, especially to future maintainers. IMHO this should not be a hard rule, but a suggestion if ordering is problematic. --=20 Regards, Bryan Drewery bdrewery@freenode/EFNet --------------enig0DA31DA713E59D992E052D5F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQrPjsAAoJEG54KsA8mwz5uoEP/i7mAZWRaANZY8F7LCskZKm5 iwSZsShGqKxKvImhw0Ti4IoHIZrauH0DzqtaSJSIGXnG3n6tnTsk/dfHpx3Mk1O4 fnaCOCFJfDv5YZikz1e3qJ8k6AvtpHAGZXVHe+cMKTM7ymKX+q/8/aNj9Tk5iAa5 /CojBBty1OyX37jXLD6RUxuStSPsswGwmLrBQG7Y1NiqZfnELsXNRt46/3eIGZ6E 8T9mHI9CifM+HBIv1w8aYAgW3IEIMXNg2r7vVQ56hsCR4QWMORN6Pkw3PNR3tIuS IuPiI1Ck4EdRUhf6CUC/7o29SO/jH62ZmO+Cu64m55Dh2vYt5nkTy+cEZ9o/QXDj MOwEG1/ukEy5dc2uGUqk9yz0dyNSXe9KCwIGBQXf1hnNYtS4Lfg0xRpF4nL1zKXU mRSPG2044OqqE2naOlh/KlBCK57386TmdATzL2ynJRUfN7pVJSdwIZoXUylNqd1J 5gZeZLXnbXPr+sIdQIh5RFn+rU8wf46Gx6V3J5xwCPwFK/gEgb0sgVoFR10hnxiM GEFMVSaPGB7OQhfyPQiLtNVlkNAI9faaQSPwn4iXDXFeiay+wKEJhX4QAnO5vibf Gz0u38cZ3CRrmh9ROw+w8IUVKy51KRQdfsD6fn3p9lp1tPtMwGLMtjnffS6qa/tQ N0P5P2lP3MePZvfc4wzI =fFg1 -----END PGP SIGNATURE----- --------------enig0DA31DA713E59D992E052D5F--