<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr"><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">Hi</span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">First, please keep your replies on list.</span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">You will need a fork if you ever wish to create a feature branch to use to submit a PR to update a port.</span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">Cheers Chris</span></div></div><div dir="ltr"><br>On 13 Aug 2019, at 7:55 pm, Gerben Wierda <<a href="mailto:gerben.wierda@rna.nl">gerben.wierda@rna.nl</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Albus:macports-ports sysbh$ git remote -v</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">origin<span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/macports/macports-ports.git" class="">https://github.com/macports/macports-ports.git</a> (fetch)</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">origin<span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/macports/macports-ports.git" class="">https://github.com/macports/macports-ports.git</a> (push)</span></div><div class=""><br class=""></div><div class="">I don't have a fork.</div><div class=""><br class=""></div><div class="">Should I work in a fork or is it OK to work like this?</div><div class=""><br class=""></div><div class="">G</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 13 Aug 2019, at 16:24, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">sudo port -d sync<br class="">( -d just means debug mode, which means you see what is actually run )<br class="">this then will in effect run<br class="">git pull --rebase --autostash origin master<br class=""></blockquote><br class="">One detail just came to my mind.<br class=""><br class="">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<br class=""><br class="">Titan ~/Projects/MacPorts/ports > git remote -v<br class="">cjones<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:cjones051073/macports-ports.git (fetch)<br class="">cjones<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:cjones051073/macports-ports.git (push)<br class="">giansalvo<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:giansalvo/macports-ports.git (fetch)<br class="">giansalvo<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:giansalvo/macports-ports.git (push)<br class="">herbygillot<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:herbygillot/macports-ports.git (fetch)<br class="">herbygillot<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:herbygillot/macports-ports.git (push)<br class="">michaelld<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:michaelld/macports-ports.git (fetch)<br class="">michaelld<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:michaelld/macports-ports.git (push)<br class="">origin<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:macports/macports-ports.git (fetch)<br class="">origin<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:macports/macports-ports.git (push)<br class="">yan<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:yan12125/macports-ports.git (fetch)<br class="">yan<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:git@github.com" class="">git@github.com</a>:yan12125/macports-ports.git (push)<br class=""><br class="">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.<br class=""><br class="">Chris<br class=""></div></div></blockquote></div><br class=""></div></blockquote></body></html>