On 05.08.2008 10:57, Peter Arrenbrecht wrote: > Why would including a fix for a situation that occurs only when > manually copying repos with hardlinks be crucial on Windows?
You are wrong here. The bug affects "hg clone", as that creates hardlinks on windows NTFS, which that opener treats wrongfully. If you feel comfortable having such a bug in such a central part of Mercurial, then please do so. I wouldn't want to have my name connected with such a release. > To cite > from the test script: > > cp -al a b > > What am I missing here? See above. > Besides, I agree with TK that unless there are very compelling reasons > to cherry-pick fixes, THg should track Hg's official releases. This > way it's much easier for people to know what Hg they've got and > communicate this in bug reports and such. Where exactly have I suggested to cherry pick? My suggestion was to use crew-stable *if* you want to push out a new release _right_ _now_, which obviously seems to be the case here, as TK doesn't seem to want to wait for that new Mercurial release, which has been talked about on Mercurial-dev. > Speaking of which, is there an official clone of the Hg repo that > tracks exactly which version of Hg was built into the THg Windows > builds, maybe with dedicated THg related tags? If not, I think it > would be a good idea to have one. > > -parren Well, folks, I really don't care what you want to push out on THG. I just posted some comments about it. It is really up to you to have a differing opinion. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
