On Mon, May 12, 2008 at 3:57 AM, Steve Borho <[EMAIL PROTECTED]> wrote:
> On Sun, 2008-05-11 at 14:01 +0200, Adrian Buehlmann wrote:
>> On 05.05.2008 06:12, Steve Borho wrote:
>> > 0.4 RC2 is now uploaded on SourceForge.
>>
>> Thanks Steve for your work.
>>
>> I do have a concern with RC2:
>>
>> RC2 uses 626cb86a6523 of Mercurial, which is only available from
>> the Mercurial _crew_ repo.
>
> Every thg installer I've built has used the tip of main from that day.
> According to my repo, that changeset is:
>
> changeset:   6570:626cb86a6523
> tag:         tip
> user:        Benoit Allard <[EMAIL PROTECTED]>
> date:        Thu Apr 24 17:16:02 2008 +0200
> summary:     add compression type type parameter to bundle command
>
> In the past, this policy has been necessary as each release has picked
> up win32 specific bug fixes from the tip of main.  However, it maybe be
> a good time to start shipping the tip of hg-stable instead.

It has been my goal to only 'link' to the latest official release of
Mercurial. But I should feel fairly comfortable with tip of hg-stable.

> For 0.4, I was hoping to include the coal web style which did not make
> it into 1.0.  But that's about the only thing in main that's not in
> hg-stable that I was interested in.
>
> I'm hoping someone will volunteer to build these packages in the near
> future, as I have less and less time to devote to them.

Naturally, I should be the one. Give me sometime to learn how to do
it. And, since I can't get PyQt to work properly on my system, it
probably mean that the binary I build will come without Qct. Though
users preferring Qct can always install it independently.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to