<div dir="ltr">I use git (and Github Enterprise) in my day to day work. I can help out. <div><br></div><div>Another good (free (as in beer)) client is SourceTree <a href="https://www.sourcetreeapp.com/">https://www.sourcetreeapp.com/</a></div><div><br></div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature">—Mark<br>_______________________<br>Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank">emer@emer.net</a>><br></div></div>
<br><div class="gmail_quote">On Fri, Aug 19, 2016 at 8:19 PM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Here are some resources GitHub recommends for learning git:<br>
<br>
<a href="https://help.github.com/articles/good-resources-for-learning-git-and-github/" rel="noreferrer" target="_blank">https://help.github.com/<wbr>articles/good-resources-for-<wbr>learning-git-and-github/</a><br>
<br>
When MacPorts moves to GitHub, committers will need to stop using their<br>
existing Subversion working copies and get a fresh copy of the code from<br>
GitHub. There will be separate repositories for base, ports, the web site,<br>
and so forth.<br>
<br>
If you are a committer or would like to contribute to MacPorts in the<br>
future, and you don't already have a GitHub account, you should create one<br>
now. If you are a committer, you should add your @<a href="http://macports.org" rel="noreferrer" target="_blank">macports.org</a> email address<br>
to your GitHub account now, so that any past commits you made in Subversion<br>
are properly associated with your GitHub account.<br>
<br>
Some of our developers are not very, or not at all, familiar with how to use<br>
git, and I include myself in that list. It would be great if we could<br>
prepare a wiki page that helps Subversion users learn to use git, perhaps<br>
with examples such as "In Subversion, to update your working copy with the<br>
latest code, you run 'svn update', while with git, you update your clone<br>
using 'git pull'". We may also need some task-related examples, such as how<br>
to create a new port; how to update an existing port; how to install an<br>
updated version of a port that was submitted as a pull request; how to fix a<br>
pull request that isn't quite correct. We may also need some explanations of<br>
git terminology, such as "master", "origin", "rebase", "fast-forward", etc.<br>
Let's use this wiki page to collect this information:<br>
<br>
<a href="https://trac.macports.org/wiki/WorkingWithGit" rel="noreferrer" target="_blank">https://trac.macports.org/<wbr>wiki/WorkingWithGit</a><br>
<br>
If you aren't familiar with git, please ask specific questions about tasks<br>
that you don't know how to do in git. If you are familiar with git, please<br>
help answer these questions.<br>
<br>
GitHub offers a nice Mac app that makes it easy to do basic tasks like<br>
committing updates without having to know how to use git on the command<br>
line.<br>
<br>
GitHub also offers a Subversion compatibility feature. If you don't know git<br>
and don't want to learn right now, you can continue to use the Subversion<br>
client as before, you'll just have to "svn checkout" a new working copy from<br>
the GitHub repository URL. You can use that working copy with your normal<br>
Subversion client and it should behave as a normal Subversion repository.<br>
<br>
______________________________<wbr>_________________<br>
macports-dev mailing list<br>
<a href="mailto:macports-dev@lists.macosforge.org">macports-dev@lists.macosforge.<wbr>org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-dev" rel="noreferrer" target="_blank">https://lists.macosforge.org/<wbr>mailman/listinfo/macports-dev</a><br>
</blockquote></div><br></div></div>