>> The queues feature in Mercurial is available independently in the >> quilt system. Mercurial makes this point: >> <http://hgbook.red-bean.com/hgbookch12.html> > >There are things with queues that you don't get with quilt. Quoting >from the book, > >"As an example, the integration of patches with revision control makes >understanding patches and debugging their effects--and their interplay >with the code they're based on--enormously easier. Since every applied >patch has an associated changeset, you can use "hg log filename" to >see which changesets and patches affected a file. You can use the >bisect extension to binary-search through all changesets and applied >patches to see where a bug got introduced or fixed. You can use the >"hg annotate" command to see which changeset or patch modified a >particular line of a source file. And so on."
Sorry, I didn't mean to start a debate about the relative feature set of the various systems. The git system can do what you want (e.g. bisect, branch, etc.). Having gone thru the series of changes cvs->arch->svn->git I understand why you would be reluctant to change. The original point was the question of regenerating the information. Since git uses hashing to guarantee uniqueness you know that any root (or subtree) with equal hashs has the same code. This makes it impossible to inject a virus. It also makes it very convenient to recreate the exact sources used by a user reporting a bug since you simply "undo the changes until the root is equal" and you have the exact sources reporting the bug. Given the high change rate of Sage this could be a major feature. Another point worth mentioning is that git only stores one copy of a file if they hash to the same value. Since the GMP library, BLAS, LAPACK or other common libraries might show up in several spkgs there is the potential for a significant reduction in storage space. I also noticed that arch and svn seem to keep a second copy of the system somewhere (not sure what hg does) but moving to git immediately reduced the required disk space by a factor of 2. For a system as large as Sage this might prove interesting. If I get the time I can try to import Sage into git to quantify the gain. Tim Daly Axiom --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
