Date: Sat, 25 Jan 2014 18:51:50 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Alfred Perlstein <alfred@freebsd.org> Cc: Yuri <yuri@rawbw.com>, freebsd-ports@FreeBSD.org Subject: Re: What is the problem with ports PR reaction delays? Message-ID: <20140125175150.GB67191@ithaqua.etoilebsd.net> In-Reply-To: <52E37C71.1060906@freebsd.org> References: <CAHcXP%2Bf6e-t--XbQPTH1goJp_CL7P=zTj5trZVWd4YZ_EsO9gw@mail.gmail.com> <52E2FA36.5080106@marino.st> <CAHcXP%2BfRDeKXjz0_sifgzeXC2dA-eDnoV5NH1yvF2D6R8JRmAg@mail.gmail.com> <52E303CB.6020304@marino.st> <CAHcXP%2Be9p2HrQ=M9HmPecMbWtXRuYPzH9kwfLGqgdrUrhvLuEA@mail.gmail.com> <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org> <52E3719B.3040503@rawbw.com> <52E37C71.1060906@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 25, 2014 at 12:57:21AM -0800, Alfred Perlstein wrote: >=20 > On 1/25/14, 12:11 AM, Yuri wrote: > > On 01/24/2014 20:16, Alfred Perlstein wrote: > >> (maybe there is some great ports system that I'm not aware of that=20 > >> makes this all as easy github, but I somehow doubt that.) > > > > github itself is closed source, but 95% of its functionality is based= =20 > > on git which is open. One only needs to invoke 3-4 git operations to=20 > > support what it does on the website side. Register on the site, fork=20 > > the project under user's login, submit a pull request, merge a fork's= =20 > > branch to the main branch. All these are basically git commands.=20 > > Without the glossiness of github, this is not that large of a project.= =20 > > Submitters will do the rest through git. > > > > I think, instead of tediously going through the PRs by hand, it is=20 > > wiser to set up some system like this. > > > Agreed. +1000 >=20 > Although if we go down the rabbit hole of building something "like=20 > github" that might take a while. For now prototyping using the github=20 > pull methods might be a good proof of concept. I may look into doing a= =20 > github pull request -> GNATS (src) PR gateway if time allows. Once again github pull request is the worst way of merging patches that exi= sts. We already have problem with ugly and inaccurate logs, such pull request wi= ll make it even worse. Making proper merge from github pull request it not that easy, you will nee= d to fetch pull request as custom branches and cherry-pick them. That is really = not convenient. regards, Bapt --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iEYEARECAAYFAlLj+bYACgkQ8kTtMUmk6EygywCgqdbWFiNuGF/9PZIdNqjWbCf6 Z5AAn1sY07FTJiY4XicQfUVocEABKbns =SwxP -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140125175150.GB67191>