On Thursday 21 July 2005 19:09, Tristan Seligmann wrote: > * Thomas Zander <[EMAIL PROTECTED]> [2005-07-20 22:38:51 +0200]: > > 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. > > Well, you *have* created a 2.0 branch; one which has the files in > question deleted. It seems entirely appropriate to treat it as > exactly what it is: a branch.
One may naively think that, by removing some files, you restore the state from before these files were created. You thus may have expected that the tag is moved back past the patches that created these files. But the changes touching the new and touching the old files may not commute. There may be patches that touch both sets of files. I would create two repositories (aka branches), a development one and a stable one. First you tag the development repo, then you copy it to create the stable repo. In the stable repo you delete all files that should be. The stable repo thus "begins" at the tag. Patches that touch only the leftover files may still be able to move between these two repos. This may make it easier to backport patches from the development to the stable repo. -erik -- Erik Schnetter <[EMAIL PROTECTED]> http://www.aei.mpg.de/~eschnett/ My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from www.keyserver.net.
pgpfw7B2MWFqf.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
