On 20/08/2016, at 1:24 PM, Lawrence Velázquez wrote:

>> On Aug 19, 2016, at 11:16 PM, Ian Wadham <iandw...@gmail.com> wrote:
>> As a KDE developer (and spectator of the changeover from svn to git) I have 
>> found
>> this cheat sheet very useful, but not quite covering all situations I have 
>> encountered.

>>  http://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf

> Any documentation we write should be written specifically for developers
> 
>       1. who are accustomed to using Subversion, and
>       2. want to translate *their MacPorts workflow* to Git.
> 
> We shouldn't expend effort rewriting a sloppier version of every generic 
> "this is how version control works" Git tutorial on the Web. There's quite 
> enough of that.

I can thoroughly recommend the cheat-sheet I referred to.  It is a good start.

It was put together by Zack Rusin, a prominent KDE and Qt developer, and
originally appeared on his blog.  It is just one page.  I quoted the PDF version
above because it is high-res and easily readable, although the web address
sounds unpromising.  When coding I keep a copy in a folder on my desktop
at all times.  I wish more Open Source software had such summaries.

So please have a look.

Cheers, Ian W.

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to