-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a pretty big source repository in Darcs and I did a 2.0 release of my project the other week. I did this in a branch and I removed a lot of things that were not ready to be released yet. Think whole subdirs here.
After recording the remove patches and a tag to state this is the 2.0 release; I have been unable to merge these patches back into the mainline since the unreleased (and thus removed) files should not be deleted from darcs in the mainline. I've chosen to keep a 2.0 branch on my server as the only place where the RELEASE2.0 tag stays, over deleting and re-adding the files I have not released in my mainline. I would be interrested to know if there are others who have better ideas of how to handle this. Thanks. - -- Thomas Zander -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFC3rZbCojCW6H2z/QRAq1OAJ4hiEbiAqk1tb8pNbiJZTHlmqMhqQCgj/Ej iSmjQ7spmU6CU3Ab8FpOH2o= =YnMv -----END PGP SIGNATURE----- _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
