Thanks Justin - that's clear.

If I want to sync my fork with branches that are newly created in the
canonical repo I would do:

git fetch geotools  # to get refs to new branches
git checkout new_branch_name
git push mbedward new_branch_name

Is that right ?

Aside: I don't think I yet fully comprehend the purpose of our
developer forks.  I'm using "Pro Git" as my reference book and its
discussion of alternative work-flows for projects, developer forks are
only mentioned in the context of very restricted access to the
canonical repo, ie. I would commit to my fork and then make a pull
request to the higher beings with canonical access.

Apologies for so many entry-level questions.

Michael


On 3 July 2012 11:47, Justin Deoliveira <[email protected]> wrote:
> Hey Michael,
>
> Again this is personal preference as there a few ways to do it (basically
> how you want to organize your remotes) but when i want to update the primary
> branches in my fork here is what i do:
>
> % git checkout master
> % git pull geotools master
> % git push jdeolive master
>
> % git checkout 8.x
> % git pull geotools 8.x
> % git push jdeolive 8.x
>
> And so on for any branch you want to sync.
>
> In my local repo my remote references look like this:
>
> % git remote -v
> geotools git@github-jdeolive:geotools/geotools.git (fetch)
> geotools git@github-jdeolive:geotools/geotools.git (push)
> jdeolive git@github-jdeolive:jdeolive/geotools.git (fetch)
> jdeolive git@github-jdeolive:jdeolive/geotools.git (push)
>
> Hope that helps.
>
> -Justin
>
>
> On Mon, Jul 2, 2012 at 7:40 PM, Michael Bedward <[email protected]>
> wrote:
>>
>> Hi Justin,
>>
>> is there a recommended work-flow for keeping our developer forks in
>> sync with the canonical branches ?
>>
>> Michael
>>
>>
>> On 3 July 2012 11:09, Justin Deoliveira <[email protected]> wrote:
>> > Hi all,
>> >
>> > The 8.x branch has been cut.
>> >
>> >   https://github.com/geotools/geotools/tree/8.x
>> >
>> > And along with it.
>> >
>> >   https://github.com/geotools/geotools/tree/rel_8.x
>> >
>> > I have also run through the paces of generating out the 8.0-RC2 release,
>> > fixing issues that resulted from the git changeover along the way. I
>> > haven't
>> > put together any of the announcements or anything. I believe Victor had
>> > something ready to go?
>> >
>> > -Justin
>> >
>> > --
>> > Justin Deoliveira
>> > OpenGeo - http://opengeo.org
>> > Enterprise support for open source geospatial.
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond.
>> > Discussions
>> > will include endpoint security, mobile security and the latest in
>> > malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > GeoTools-Devel mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/geotools-devel
>> >
>
>
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to