Max Battcher writes: > > Hm. I would suppose that the only way to get a dependency on a > > tag would be an explicit dependency (eg via "darcs commit > > --ask-deps"). Using "darcs unrecord" would be a little > > risky[...]. But it seems like it could work in principle. > > In practice though, I think it would probably make more sense in darcs just > to make a (auto-) clone repository for your "moving tag"... That is just > create a "latest-clean" repository and keep that up-to-date (just as you > might have a "stable", or "buildbot-approved" repository).
Note that we're not talking about "me" here, we're talking about the "official" Darcs repo. > Also, I think that your unrecord then re-tag situation won't work in > practice (due to other patches depending on your tag) without modifications > to darcs. How can a patch depend on a (non-checkpoint) tag? (Without an explicit dependency, that is.) I thought a tag was basically an empty patch. How can that not commute? _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
