Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Nov 2012 18:53:24 +0400
From:      Eygene Ryabinkin <rea@freebsd.org>
To:        Erwin Lansing <erwin@FreeBSD.org>
Cc:        svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Andrey Chernov <ache@freebsd.org>, Chris Rees <utisoft@gmail.com>, ports-committers@freebsd.org
Subject:   Re: svn commit: r307612 - in head/misc/astrolog: . files
Message-ID:  <P1kYGGwXBWZ1fcuxwnoQYoZ6uu0@7TEDb4Yy37iQCK/hgFqwmvLmFqM>
In-Reply-To: <20121121120128.GC4474@droso.net>
References:  <201211210949.qAL9nl4a018306@svn.freebsd.org> <CADLo83-Yf0vt73kynPPJPCEcLex11g=SzJshbqmyr=bmHWaKUA@mail.gmail.com> <50ACB0A7.1030108@freebsd.org> <CADLo839jgAP_V3F4x%2BwSaFk65rLdvS-pPhaM7krP9FWHn5cFfA@mail.gmail.com> <50ACBE7D.70203@freebsd.org> <20121121120128.GC4474@droso.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--OwLcNYc0lM97+oe1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:
> >=20
> > Yes, but the new naming convention is something which should be decided
> > 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 mome=
nt,
> > so I prefer to stay the old one I see.
>=20
> "Please only use characters [-+._a-zA-Z0-9] for naming your patches. Do
> not use any other characters besides them. Do not name your patches like
> patch-aa or patch-ab etc, always mention the path and file name in patch
> names."
>=20
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/slow-pa=
tch.html
>=20
> Imporovements to the handbook are of course always welcome.

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.

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
Eygene Ryabinkin                                        ,,,^..^,,,
[ Life's unfair - but root password helps!           | codelabs.ru ]
[ 82FE 06BC D497 C0DE 49EC  4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]

--OwLcNYc0lM97+oe1
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iF4EABEIAAYFAlCs6uMACgkQFq+eroFS7PuOlQD/VKMbTAn4wT5lkwwyJa7UcNaw
o1pDzQk3Xjmuw6KcTJMA/RJgXCPFNRUdcIv5OGjdUo58eXuDwKmglremQ0cxGmuN
=peuk
-----END PGP SIGNATURE-----

--OwLcNYc0lM97+oe1--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?P1kYGGwXBWZ1fcuxwnoQYoZ6uu0>