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: Wed, 22 Jan 2020 10:23:00 -0000 [thread overview]
Message-ID: <41e8a9a3-2df5-3a9f-85b2-488917716ebd@arm.com> (raw)
In-Reply-To: <d3e5e937-2808-8c90-67af-5dcba36e1e6f@arm.com>
On 22/01/2020 10:04, Richard Earnshaw (lists) wrote:
> On 21/01/2020 23:23, Hans-Peter Nilsson wrote:
>>> From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
>>> Date: Tue, 21 Jan 2020 14:36:32 +0100
>>
>>> 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.
>>
>> (typo "bransh")
>>
>
> Duh! will fix before push.
>
>> Thanks, this and your previous reply certainly helped!
>>
>
> Yes, I saw from the gcc-cvs list that you were merrily pushing now.
>
>> Any chance of a git-add-user-branch.sh too, while you're at it?
>> Or maybe it's just the corresponding push command in there,
>> that's needed.
>>
>
> On the todo list... unless someone beats me to it. Mean-time my
> gitwrite.html patch describes how to set up a user branch.
>
> R.
>
>> brgds, H-P
>>
>
Now pushed.
R.
prev parent reply other threads:[~2020-01-22 10:09 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)
2020-01-22 0:51 ` Hans-Peter Nilsson
2020-01-22 10:18 ` Richard Earnshaw (lists)
2020-01-22 10:23 ` 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=41e8a9a3-2df5-3a9f-85b2-488917716ebd@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).