On Tue, Aug 5, 2008 at 9:09 AM, Adrian Buehlmann <[EMAIL PROTECTED]> wrote: > On 05.08.2008 04:01, TK Soh wrote: >> On 8/4/08, Adrian Buehlmann <[EMAIL PROTECTED]> wrote: >>> On 04.08.2008 11:10, TK Soh wrote: >>>> On Mon, Aug 4, 2008 at 8:13 AM, Adrian Buehlmann <[EMAIL PROTECTED]> >>>> wrote: >>>>> On 04.08.2008 09:02, TK Soh wrote: >>>>>> Greeting! >>>>>> >>>>>> The installer for 0.4 RC4 is now available for download on SourceForge. >>>>>> >>>>>> http://sourceforge.net/project/showfiles.php?group_id=199155 >>>>>> >>>>>> Please checkout the release note for the list of changes: >>>>>> >>>>>> >>>>>> http://tortoisehg.sourceforge.net/hg/tortoisehg-dev/file/864497951b6b/ReleaseNotes.txt >>>>>> >>>>>> In addition to the the changes specific to TortoiseHg, this installer >>>>>> also includes the latest Forest extension (rev 715440e45bf4, dated >>>>>> 28-Jan-2008). >>>>>> >>>>>> Like 0.4rc3, 0.4rc4 is also linked to Mercurial 1.0.1. >>>>> What's the point in not including >>>>> http://hg.intevation.org/mercurial/crew-stable/rev/08d9e0f974d9 >>>>> if you push out a new release right now ? >>>> Because we are releasing for TortoiseHg. Not Mercurial. >>>> >>>> If any of these changes are so critical, I'm sure Matt will cut a >>>> release for Mercurial for them. Then by policy, TortoiseHg shall link >>>> to the whichever latest release of Mercurial. >>> It's rather silly to push out a release having major known bugs like >>> the one fixed in 08d9e0f974d9 >> >> You appear to have missed my point. I strongly suggest you direct the >> question to Matt and the team on the release of Mercurial to address >> these 'major known bugs'. > > I fail to see what this has to do with Matt, as he certainly doesn't > care what policies you want to follow or not on THG. > > On another note, Matt would certainly not push out a new release > of Mercurial that contains a major bug for which there is > an easy fix (one that can be reviewed in 30 seconds) in crew-stable > available. > >> TortoiseHg's policy stays. > > Of course you are free to use whatever you think is good for your > project. After all, it's your project.
Why would including a fix for a situation that occurs only when manually copying repos with hardlinks be crucial on Windows? To cite from the test script: cp -al a b What am I missing here? 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. 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 ------------------------------------------------------------------------- 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
