Hi, > Wait... I just re-read your post. Tell me if I'm right. Your whole > beef with other SCMs is that you have to type: > > myscm push http://some-repository.org > > Is that the issue that you and Michael are talking about? That you > have to specify the URL of the place you are pushing to the first time > you push? For some value of "beef", yes.
I don't have to tell fossil or hg or bazaar where to push - they know it based on where I cloned from. The distinction is that in fossil I have one repository on my machine and I open multiple working sets on the same repository. When I push or pull, it is always with the parent of that one repository. In hg or bazaar I clone the repository each time I want a new working set. When I push or pull _by default_ (i.e. I don't explicitly specify the repository) it will be with the parent, which in some cases will be a REMOTE and in other cases another local repository. Always explicitly specifying the remote repository is safest because it avoids this confusion; if you don't then you have to be exceedingly careful that you understand which repository you are pushing to or pulling from. A similar problem occurs when pulling down changes (to update and merge). With fossil you have one repository and multiple working folders. So you commit in one working folder, and update in the other folders. With bazaar and hg you commit to your repository which is local to your working set, so you must push/pull the change to other working folders. Regards, Twylite _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
