On Tue, Aug 5, 2008 at 11:58 AM, Adrian Buehlmann <[EMAIL PROTECTED]> wrote:
> On 05.08.2008 10:57, Peter Arrenbrecht wrote:
>> 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.
>
> Besides, what's so difficult about
>
>> hg version
> Mercurial Distributed SCM (version 626cb86a6523+tortoisehg)
>
> when reporting bugs?
Not so difficult when reporting, agreed. But rather harder to get a
feel for whether this already contains a specific bugfix or not when,
for instance, trying to help people on IRC. Much easier to remember of
Hg 1.0.1 contains a fix, than all the hex ids floating around.
>
> The first string ("626cb86a6523") identifies the Mercurial part
> of THG.
>
> I haven't checked how to identify the THG part on the command
> line. But it can be seen in the about dialog, which in my
> example shows:
>
> '''
> TortoiseHg (version 0.4rc2)
> with Mercurial-626cb86a6523+tortoisehg, Python-2.5.1, PyGTK-2.10.6,
> GTK-2.10.11
> '''
>
-------------------------------------------------------------------------
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
