Subject: Re: [boost] Post-git forking process
From: Daniel James (dnljms_at_[hidden])
Date: 2014-03-28 07:37:47
On 27 March 2014 14:01, Bjorn Reese <breese_at_[hidden]> wrote:
> On 03/27/2014 02:14 PM, Daniel James wrote:
> If you're only changing one module at a time, forking the super project is
>> probably more trouble than it's worth. But if you need to, I think it
> I do not know if I need to. I was just following the description.
> What is the procedure for making pull-request to a single module without
> forking the super project?
I assume you already have a full check out of master. To create your branch:
- Go to the repos' page and click the 'fork' button to create a fork.
- Copy the 'ssh clone url' from the right hand side.
- In the local copy of the module:
git remote add remote-name (paste url here)
git checkout origin/develop -b feature/branch-name
git push --set-upstream remote-name feature/branch-name
Now when you push changes it should go to your fork.
You can create the pull request through the web interface, although be
careful to make it against 'develop'. When you update the modules from the
super project (using 'git submodule update --init'), it might put you back
on the upstream branch, so you need to remember to checkout your branch
when you want to work on it. That's a bit of a pain, but for a single
module it's less work than managing changes to the super project.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk