Date: Sat, 27 Apr 2024 06:06:33 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: Emmanuel Vadot <manu@FreeBSD.org>, ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: ab5f2419c25e - main - x11/xwayland-run: Add new port Message-ID: <bk5v-cuuu-wny@FreeBSD.org> In-Reply-To: <20240426132919.808494b0d75821c15f494656@bidouilliste.com> (Emmanuel Vadot's message of "Fri, 26 Apr 2024 13:29:19 %2B0200") References: <202311291352.3ATDql0j066996@gitrepo.freebsd.org> <34rc-gieb-wny@FreeBSD.org> <20240424083543.39ab381c632ef32035a0a837@bidouilliste.com> <4jbp-1pg3-wny@FreeBSD.org> <20240426132919.808494b0d75821c15f494656@bidouilliste.com>
index | next in thread | previous in thread | raw e-mail
Emmanuel Vadot <manu@bidouilliste.com> writes: >> Fair point. I find bugzilla/phabricator workflow has too much overhead >> for lots of trivial changes across many ports. It's OK for complex >> changes but those are rare in ports/, except when adding new ports. > > What I read is : "I want to commit directly without anyone reviewing > my changes because I'm too lazy to git arc create" In ports/ the primary entrypoint for anything is Bugzilla. exp-runs requires Bugzilla, bug auto-assignment requires Bugzilla, "maintainer timeout" requires Bugzilla (I had at least one committer complain). In teams Bugzilla forwards activity to maillists which promotes participation by non-committers. Phabricator is better than Bugzilla but worse than Git* pull requests: - cannot checkout the tree if patches fail to apply (common in ports/) - cannot import patches without arcanist (while preserving commit author/date) - cannot view combined diff (to see a big picture) - cannot edit comments to fix mistakes, rephrase, etc. I admit my workflow is inefficient but Phabricator is certainly not a solution.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bk5v-cuuu-wny>