Date: Wed, 2 Mar 2016 22:38:07 -0500 From: Jason Unovitch <junovitch@FreeBSD.org> To: Greg 'groggy' Lehey <grog@FreeBSD.org> Cc: Alexey Dokuchaev <danfe@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r410002 - in head/graphics/hugin-2016: . files Message-ID: <20160303033807.GA33553@Silverstone.nc-us.unovitch.com> In-Reply-To: <20160303032240.GF71035@eureka.lemis.com> References: <201603030313.u233Dl3P066020@repo.freebsd.org> <20160303031515.GA21075@FreeBSD.org> <20160303032240.GF71035@eureka.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Thu, Mar 03, 2016 at 02:22:40PM +1100, Greg 'groggy' Lehey wrote: > On Thursday, 3 March 2016 at 3:15:15 +0000, Alexey Dokuchaev wrote: > > On Thu, Mar 03, 2016 at 03:13:47AM +0000, Greg Lehey wrote: > >> New Revision: 410002 > >> URL: https://svnweb.freebsd.org/changeset/ports/410002 > >> > >> Log: > >> New port hugin-2016, bleeding edge version of graphics/hugin. > > > > Looks like it was not repocopied, may I ask why? > > The simple answer is "because there's no mention of that in the > Porter's handbook". The more complicated answer is "When do I need to > repocopy, and how do I do it?". Clearly this is something that needs > to go into the documentation. > It is in the committer's guide. https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html#ports-qa-repocopies > Is this such a sin that I should remove it and do a repocopy? My gut > feeling is that that would make even more of a mess. Yes. It should be removed, committed, and repocopied. This has come up in the past and can be found on the mailing list archives. Here's an example. https://lists.freebsd.org/pipermail/svn-ports-all/2016-January/113777.html > > Greg > -- > Sent from my desktop computer. > Finger grog@FreeBSD.org for PGP public key. > See complete headers for address and phone numbers. > This message is digitally signed. If your Microsoft MUA reports > problems, please read http://tinyurl.com/broken-mua -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJW17GZXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2 RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuirsH/Rk6ksPh/6PygCqHTEVMaPTR gT426zz0OMgdyqoM4mm8+YUUpF1yM00HvtDS7AeHU0z34qWZoCyFNThvgU5f1R6X p8GBGL/BtQZo8jA283DGXzx4qW7B4CdFnxTi879geT+d1MhBiJOgrmWCL8cn+5eV luzGVBTlqM+WetFCQyXkUnm3qKSyRXWcJGXF1kvXxdQB7Rrm6Ybnxl8lguCLVfuL d8z3sbuwWkvWH0HYcZjAvAZ80EDDTxiK3P+vpFGmRRscmODa17ADpYZzFN8E0ZV1 A40qbqJ+dzkdRImFopINXb6mhP6/ZPWL2XkTWK9mha+1ULZ9dCk2CU/bQ4QfaXs= =UoJp -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160303033807.GA33553>