[Sugar-devel] Managing github forks

[Daniel Narvaez]

I wonder if keeping origin on read only git, upstream on the main repo ssh
and fork on the fork ssh would work well. You wouldn't risk to accidentally
push to main repo that way.


On 29 May 2013 14:53, Manuel Quiñones <manuq at laptop.org> wrote:

> 2013/5/29 Daniel Narvaez <dwnarvaez at gmail.com>:
> > On 28 May 2013 02:10, Manuel Quiñones <manuq at laptop.org> wrote:
> >>
> >>
> >> Yes, this works well but you should be more careful whlie hacking,
> >> because a wrong push could mess the main repository (calling commands
> >> in the wrong order, for example).  Personally I hack in my own fork,
> >> and when I put my reviewer hat I switch to the main repository
> >> directory.
> >
> >
> > So the source directory in sugar-build is your fork and you keep another
> > directory for the main repository? How do you build the main repository
> or
> > you just use it to push?
>
> You have a point here.  I have the main repos inside sugar-build and
> my forks outside.  I manually maintain the two directories, moving
> patches around.. maybe I am complicating things.
>
> --
> .. manuq ..
>



-- 
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130529/db67c983/attachment.html>