On 16/01/2020 15:00, Jakub Jelinek wrote:
On Wed, Jan 15, 2020 at 10:48:23PM +0000, Joseph Myers wrote:
A reasonable replacement for those push rules might be command aliases
(e.g. "git upush <branch>" to push the user branch <branch>).
Would we have then separate aliases for pushing to one vendor branch and
another vendor branch?
Couldn't one alias determine from the branch remote and merge and
perhaps the fetch rules figure out the right git push arguments
given the setup (e.g. treat $(git config --get gcc-config.userpfx)
and $(git config --get gcc-config.user) as push to user branch,
devel/*, master, releases/* as normal git push and the rest as vendors
(or let git-fetch-vendor.sh record list of all used vendors in some gcc-config
setting)?
Jakub
I think the new proposed remotes structure should eliminate most of the
concerns about unsafe push rules; at worst you will only push everything
related to the 'remote' that your current branch is on.
So I think having more aliases is now unnecessary.
R.
