Claus Reinke wrote:
Perhaps the rumours refer to non-tagged "versions"? In conventional
non-distributed version control systems, one
might go back to the version on a specific date, while with
darcs, that only makes sense wrt a specific repo (I think?).
So you can unpull all patches after a date from your local
repo, but that doesn't mean that you get a repo that matches
someone else's repo after they perform the same procedure.
If both parties commit to a central repo, and pull all changes
via that, there is a greater chance of date-based synchronicity.
If you are releasing a software build and want a way of returning to
that exact build without having to add a tag, you can store the output
of "darcs changes --context" in a file. We store contexts of released
builds in our customer records so we can get back to any build using
"darcs get --context=context_file".
Steve
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
