On 3/3/2011 1:26 PM, Manu Abraham wrote:
>
> Actually, for newbies to get started you don't even need to know all
> the mercurial commands
>
> A quick n' dirty way to get started would be as simple as 5 commands
>
> - Creating a repository
>
> hg init: create a new repo
> hg addremove: addremove files in one go
>
> - Working on the repository
>
> hg clone: if you want to clone another repository
> hg commit: commit your changes
> hg log: view the commit logs
>
> I don't think a VCS usage can be any simpler to get started.

How does mercurial mesh with an existing IDE? For example, say I'm=20
writing code in some compiler using the compilers code editor and=20
periodically saving edits.  Does mercurial watch this and grab the saved=20
edits? How does it know when I want to save something?  Do I have to=20
alt-tab out to mercurial, run some command line, and then go back to=20
writing code?  Or do I code all day and then make copies of my work into=20
some mercurial folder?  Basically, is it working in the background=20
continually on my behalf or do I have to invoke it to do stuff for me?

I've never been exposed to a version control system, obviously.

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.