Maintaining mono/.net

[Ivan Radovanovic]

On 07/05/2016 18:06, Russell Haley wrote:
>
> The rub with GitHub is that
> there is no way to auto-magically keep a fork up to date, meaning as
> soon as you create a fork and apply patches, it becomes possible to
> get out of date without manual updates. That means it becomes the
> teams job to make sure we keep our repositories current (or get all
> patches pushed upstream).
>
> So, there are three ways that I know of to sync your changes *assuming
> they under git currently*:
> 1) via pull requests
> 2) via raw patches
> 3) switching the remote origin, pulling the changes, then switching again (?)
>
> I have to go now, so let us know where your changes are. I'm not sure
> if you can create pull requests between forks of the same repo, it
> will be neat to try. If you are unfamiliar with pushing your changes
> back to your remote repository, I always used this:
>
> https://rogerdudler.github.io/git-guide/
>

My idea of doing this was something like this (I am much less familiar 
with github):

$ git clone url-to-mono-rep
$ git checkout branch-4.4
$ git branch freebsd
$ git checkout freebsd
... doing some work ...
$ git remote add freebsd url-to-our-rep
$ git push freebsd freebsd	# pushing freebsd branch to our repo

for pulling new development from mono
$ git checkout master
$ git pull origin master

merging mono changes with ours
$ git checkout freebsd
$ git merge master

(warning: high probability that I made some mistake with git commands above)

In addition to this "freebsd" branch we should have one more stable 
branch, which would require code to be reviewed to reach it.

P.S.
I got invite for github (thanks Russ!), I will first test how to push 
this with some dummy remote I will create (in my experience mistaken 
commits to central repository can be annoying to fix).