Commits

spek committed b66f21f

- pre-publish changes

  • Participants
  • Parent commits 374e6d4

Comments (0)

Files changed (1)

using_dcvs_part1-commit-push-log.html

-<p>This document outlines the very basics of using a Distributed Concurrent Version System (DCVS) to manage and store changes and updates to documents you write. Used primarily for software code, I've come to use it for my blog posts, poetry, documentation etc. If you've never heard of Concurrent Versioning Systems before, you might want to do a quick search online for what they do, and some of the terminology: repository and commit to be specific.</p>
+<p>This document is the first in a series that outlines the very basics of using a Distributed Concurrent Version System (DCVS) to manage and store changes and updates to documents you write. Used primarily for software code, I've come to use it for my blog posts, poetry, documentation etc. If you've never heard of Concurrent Versioning Systems before, you might want to do a quick search online for what they do, and what they are for.</p>
 
 <p>Back in the day, I used software such as CVS and SVN to house my code changes. This was tedious though. I had to set up a server, keep it running 24x7, ensure it was properly backed-up and maintained. I worked at an ISP, so these things weren't a problem for me. However, for others, having a dedicated server doesn't make a lot of sense.</p>
 
 steve@ub:~/repos/test$ hg log -r 0 -r 2
 </pre>
 
+<p>I'll end this post here. You've learnt the very basics on how to clone a Mercurial repository from your free Bitbucket account, how to commit changes into changesets, how to push the changesets back into the master repository, and how to do some basic review of the changes that you've made. In the next episode, we'll delve into how you can compare changes against each other, reverting your working directory to a previous change, creating branches to manage different change tracks and an explanation and examples of how DCVS differs from non-distributed CVS systems.</p>
 
+<p>Thanks for reading. If you've read any of my other posts, you know I appreciate all feedback, good and/or bad in either the comments below, or privately via <a href="mailto:steve.bertrand@gmail.com">email</a>.</p>
 
 
 
 
+
+