Michael Richter wrote: > Do you read before you respond? My specific beef was given and it has > nothing to do with specifying where I'm pushing to. (Hint: *lost work*.)
Huh? You will not lose any work doing what you did: ~/B $ darcs initialize ~/B $ darcs pull ../A ~/B $ touch 3 ~/B $ darcs add 3 ~/B $ darcs record ~/B $ rm -r ~/A ~/B $ darcs push <error> No work lost. There is nothing in "A" that "B" needs. Really. > Because, Sparky, when you clone a repo in fossil you have a repository > file. That repository file contains the original place you cloned from > within it. See my reply to Twylite. Maybe this is how fossil works, but other SCMs have no such thing. Instead, they remember where you pushed or pulled from last time (to save typing). There is no "parent" unless you go out of your way to make "light-weight branches". Btw, apparently Hg doesn't even support light-weight branches. > You have to *open* said file to get your working set Maybe in Fossil, but not in the SCMs you are criticizing. Just push or pull from some other place and the SCM will switch to that other location as the default. > So when you say "fossil commit", fossil > knows where to commit because, get this, your working set comes from a > repository and has it recorded all automagically-like. Every distributed SCM knows where to commit when I say "commit". They all commit to the current branch. > That whole separation of concerns thing is what I like about Fossil and > what I didn't like about Mercurial or Darcs. I think you don't understand Mercurial or Darcs. > With Darcs and Mercurial both > I've accidentally turfed repositories that held data as yet > un-propagated because I'd forgotten that I'd cloned them to do some work > and pushed locally. No. Sorry, but you don't know what you are talking about. Let's see your example again: ~/B $ darcs initialize ~/B $ darcs pull ../A ~/B $ touch 3 ~/B $ darcs add 3 ~/B $ darcs record ~/B $ rm -r ~/A ~/B $ darcs push <error> After this, B still has everything that it got when it pulled from A. B is a branch. Anyways, I think we'll both agree that Fossil is not for me, so I won't stay here very long. Daniel. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
