I really haven't experimented with anything but Git yet, and that's because:
- git-svn works really nicely, so it fairly easy to work in Git with $WORK's svn server.
- GitHub is brilliant. The UI is really nice and really helps explain Git's branching system of commits to people new to branching repositories.
- Having code I want to poke around with already up on GitHub is very convenient. Apart from Rakudo and perl6-examples, Test-More and Email-Sender are already there, and ripe for the branching.
My only complaint: unlike SVN, TortoiseGit isn't good enough for non-programmer usage just yet. The Windows Git GUI is much better, but with TortoiseSVN my non-programming workmates immediately understood how it worked. Git, with all its local/remote branching and whatnot, is a whole lot more complicated. Still, easy branching is an advantage hard to overlook, so I'll stick with Git and GitHub for now.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.