Hi First, please keep your replies on list.
You will need a fork if you ever wish to create a feature branch to use to submit a PR to update a port. Cheers Chris > On 13 Aug 2019, at 7:55 pm, Gerben Wierda <gerben.wie...@rna.nl> wrote: > > Albus:macports-ports sysbh$ git remote -v > origin https://github.com/macports/macports-ports.git (fetch) > origin https://github.com/macports/macports-ports.git (push) > > I don't have a fork. > > Should I work in a fork or is it OK to work like this? > > G > >>> On 13 Aug 2019, at 16:24, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: >>> >>> >>> 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 g...@github.com:cjones051073/macports-ports.git (fetch) >> cjones g...@github.com:cjones051073/macports-ports.git (push) >> giansalvo g...@github.com:giansalvo/macports-ports.git (fetch) >> giansalvo g...@github.com:giansalvo/macports-ports.git (push) >> herbygillot g...@github.com:herbygillot/macports-ports.git (fetch) >> herbygillot g...@github.com:herbygillot/macports-ports.git (push) >> michaelld g...@github.com:michaelld/macports-ports.git (fetch) >> michaelld g...@github.com:michaelld/macports-ports.git (push) >> origin g...@github.com:macports/macports-ports.git (fetch) >> origin g...@github.com:macports/macports-ports.git (push) >> yan g...@github.com:yan12125/macports-ports.git (fetch) >> yan g...@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 >
