hmmm, thanks for all that Fenix
your explanation is very helpful -
the tutorial was a bit over my head
I found this PDF "Distributed revision control with Mercurial" which has a bit more of an introduction
http://hgbook.red-bean.com/hgbook.pdf (or same online:
http://hgbook.red-bean.com/hgbook.html)
Neither, unfortunately, clearly explain the basic principles (like most experts they presume you know a certain amount all ready .. in fairness the PDF is
quite good that way)
I suspect I'd consider this too much of a learning process considering I'm
fairly happy with FileHamster
But I'll chance asking a couple of basic questions (if you do answer you can keep it simple/basic cause as I say I'm unsure if I'd want to invest the time in this now):-
1) Is this correct (roughly!) ? -
The basic idea is that revisions are created locally (automatically when I save files?) and then after a period of time, these revisions are [manually?] synched with another location (or the reverse, originals + revisions in another location and synched to local directory)
2) could I e.g. use Amazon S3 as a location?
3) is there a lot of maintenance work involved?
4) would you say it's flexible - e.g. with FileHamster I can say: "Ignore *.pdf files" or "ignore this folder" or "ignore
this file"
4a) Could project location be moved to a different directory - FH has a certain amount of flexibility there - the backups can be easily moved
5) if I had a bunch of projects is it easy to keep track of them
6) Damn, I've forgotten #6
thanks, Tom
Recent Posts
ouch 
