On Thu, Mar 27, 2008 at 03:34:15AM +0000, Declan Naughton <[EMAIL PROTECTED]> wrote: > In revision control systems like Mercurial and git, every time the > repository is updated (recorded to in darcs terms) a new revision > identifier is associated with it's new state, so that it can be > referred to for checkouts and such. > > In darcs, users MUST MANUALLY use tags, this I consider quite a > downfall. Would it be a bad or a good idea for darcs to checksum the > context and record this with records, and, (being the revision > identifier) printing this out in 'darcs changes', providing for 'darcs > get --rev=xxxxxxxxx' etc? > > Or what am I overlooking?
yes, and no :) in git, you operate with trees. in darcs, you operate with patches. so if you want to have a given state of the tree, then you need tags, yes. though, every patch has a hash, so in most cases, a darcs get --to-match "hash foo.gz" should do what you need. but definitely this is a feature, not a shortcoming, i think.
pgpAnfWsMPvaU.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
