Date: Thu, 28 Jan 2010 22:44:35 +0200 From: Ion-Mihai Tetcu <itetcu@FreeBSD.org> To: Stephen Montgomery-Smith <stephen@missouri.edu> Cc: freebsd-ports@freebsd.org Subject: Re: patch upgrade for port committers? Message-ID: <20100128224435.6186f281@it.buh.tecnik93.com> In-Reply-To: <4B61E988.1000801@missouri.edu> References: <4B61E988.1000801@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/3DlPtnniuffc6eJid+tDbJB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 28 Jan 2010 13:46:16 -0600 Stephen Montgomery-Smith <stephen@missouri.edu> wrote: > When an update to a port is committed, it is likely to contain >=20 > (a) lines like "Only in xxxx: yyyy" >=20 > or (b) patches that are created against empty files using the "-N"=20 > option for diff. >=20 > Cannot "patch" honor these cases? As a port maintainer, I have been=20 > caught quite a few times by committers not adding or removing files > from the "files" directory in a port. No, what happens is that when new files are created by 'patch < something.diff' one had to=20 'cvs add path/to/file' and one sometimes forgets. --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B --Sig_/3DlPtnniuffc6eJid+tDbJB Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkth9zoACgkQJ7GIuiH/oeWJnACgnCeIq1s3x5AsGs3AJT+wjWuk HEQAoLOzdulzBIx+nNyUmMbWS07sDGhv =iKae -----END PGP SIGNATURE----- --Sig_/3DlPtnniuffc6eJid+tDbJB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100128224435.6186f281>