From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Jakub Jelinek <jakub@redhat.com>, Joseph Myers <joseph@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [patch] contrib: Don't add push rules for personal and vendor spaces.
Date: Fri, 17 Jan 2020 13:19:00 -0000 [thread overview]
Message-ID: <c817be68-8a69-83c6-a5c2-3bc49decdd81@arm.com> (raw)
In-Reply-To: <20200116150021.GF10088@tucnak>
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.
prev parent reply other threads:[~2020-01-17 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 16:47 Richard Earnshaw (lists)
2020-01-15 12:12 ` Richard Earnshaw (lists)
2020-01-15 23:51 ` Joseph Myers
2020-01-16 15:59 ` Jason Merrill
2020-01-16 16:01 ` Jakub Jelinek
2020-01-17 13:19 ` Richard Earnshaw (lists) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c817be68-8a69-83c6-a5c2-3bc49decdd81@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).