What am I forgetting?
Chris Jones
jonesc at hep.phy.cam.ac.uk
Tue Aug 13 14:24:45 UTC 2019
> sudo port -d sync
>
> ( -d just means debug mode, which means you see what is actually run )
>
> this then will in effect run
>
> git pull --rebase --autostash origin master
One detail just came to my mind.
In your clone, make sure the 'origin' remote is the main macports one,
and not some other clone. This helps make things run a bit smoother. You
can then have as many other remotes as you want, for various forks. e.g.
I (currently) have
Titan ~/Projects/MacPorts/ports > git remote -v
cjones git at github.com:cjones051073/macports-ports.git (fetch)
cjones git at github.com:cjones051073/macports-ports.git (push)
giansalvo git at github.com:giansalvo/macports-ports.git (fetch)
giansalvo git at github.com:giansalvo/macports-ports.git (push)
herbygillot git at github.com:herbygillot/macports-ports.git (fetch)
herbygillot git at github.com:herbygillot/macports-ports.git (push)
michaelld git at github.com:michaelld/macports-ports.git (fetch)
michaelld git at github.com:michaelld/macports-ports.git (push)
origin git at github.com:macports/macports-ports.git (fetch)
origin git at github.com:macports/macports-ports.git (push)
yan git at github.com:yan12125/macports-ports.git (fetch)
yan git at github.com:yan12125/macports-ports.git (push)
so 'origin' is the primary source, and the others are either my own
fork, or others I have added to work with feature branches now and then.
Chris
More information about the macports-users
mailing list