From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] contrib: script to create a new vendor branch
Date: Tue, 21 Jan 2020 14:14:00 -0000 [thread overview]
Message-ID: <d5f508be-420d-60af-509a-538b05c2d429@arm.com> (raw)
In-Reply-To: <59281770-ec14-177e-b509-a53c86a4b7b7@arm.com>
On 21/01/2020 13:29, Richard Earnshaw (lists) wrote:
> This script is intended to create a new vendor branch. Doing so is not
> completely obvious if
> you are not familiar with the upstream structure, so this takes the pain
> out of getting it right.
>
> It doesn't check out the branch locally, but does set everything up so
> that, if you have push enabled for your vendor branches, then
>
> Â git push vendors/<vendor> <branch>
>
Correction, the branch should be named <vendor>/<branch>, so the push
should be
git push vendors/<vendor> <vendor>/<branch>
For example, for the ARM vendor, the push would be
git push vendors/ARM ARM/<branch>
R.
> will work as expected.
>
> Run the script as
>
> contrib/git-add-vendor-branch.sh <vendor>/<branch> <start-point>
>
> the <vendor> space must have previously been set up in the way
> git-fetch-vendor.sh expects.
>
> Â Â Â Â * git-add-vendor-bransh.sh: New file.
>
>
next prev parent reply other threads:[~2020-01-21 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 17:35 contrib: New remotes structure for vendor and personal refs Richard Earnshaw (lists)
2020-01-17 12:08 ` [v2] " Richard Earnshaw (lists)
2020-01-20 10:43 ` Richard Earnshaw (lists)
2020-01-21 2:07 ` Hans-Peter Nilsson
2020-01-21 2:19 ` Hans-Peter Nilsson
2020-01-21 10:54 ` Richard Earnshaw (lists)
2020-01-21 11:20 ` Richard Earnshaw (lists)
2020-01-21 14:09 ` [patch] contrib: script to create a new vendor branch Richard Earnshaw (lists)
2020-01-21 14:14 ` Richard Earnshaw (lists) [this message]
2020-01-22 0:51 ` Hans-Peter Nilsson
2020-01-22 10:18 ` Richard Earnshaw (lists)
2020-01-22 10:23 ` Richard Earnshaw (lists)
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=d5f508be-420d-60af-509a-538b05c2d429@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.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).