thg 2.5, hg 2.3.1, and check your extensions at the door

27 views
Skip to first unread message

Dave S

unread,
Sep 12, 2012, 1:38:17 PM9/12/12
to mercurial
Having tripped over THG issue 2140 (now marked as a duplicate of
2090), I think it may be worthwhile to remind users here that you made
need to update some of your extensions (or at least disable them while
waiting for upgrades) to use the latest Mercurial and Tortoises. In
my case, it was hg subversion. If you're using just the bundled
extensions, this may not apply to you.

And a reminder for us quick-witted Windows users, we probably are
looking for the file
c:\users\USERNAME\mercurial.ini

/dps

--
test signature -- please apply at front gate on Tuesdays only.
_______________________________________________
Mercurial mailing list
Merc...@selenic.com
http://selenic.com/mailman/listinfo/mercurial

Dave S

unread,
Sep 12, 2012, 2:00:27 PM9/12/12
to mercurial
On Wed, Sep 12, 2012 at 10:38 AM, Dave S <snide...@gmail.com> wrote:
> Having tripped over THG issue 2140 (now marked as a duplicate of
> 2090), I think it may be worthwhile to remind users here that you made
> need to update some of your extensions (or at least disable them while
> waiting for upgrades) to use the latest Mercurial and Tortoises. In
> my case, it was hg subversion. If you're using just the bundled
> extensions, this may not apply to you.
>
> And a reminder for us quick-witted Windows users, we probably are
> looking for the file
> c:\users\USERNAME\mercurial.ini
>

Would it be appropriate for installer packages to give you warnings to
check your unbundled extensions when you're updating?

Augie Fackler

unread,
Sep 12, 2012, 6:47:11 PM9/12/12
to Dave S, mercurial

On Sep 12, 2012, at 12:38 PM, Dave S wrote:

> Having tripped over THG issue 2140 (now marked as a duplicate of
> 2090), I think it may be worthwhile to remind users here that you made
> need to update some of your extensions (or at least disable them while
> waiting for upgrades) to use the latest Mercurial and Tortoises. In
> my case, it was hg subversion. If you're using just the bundled
> extensions, this may not apply to you.

FWIW, I'm hoping to do an hgsubversion release shortly. Sorry about the delay in getting a 2.3.x compatible release out the door.

Dave S

unread,
Sep 18, 2012, 3:29:33 AM9/18/12
to mercurial
On Wed, Sep 12, 2012 at 11:00 AM, Dave S <snide...@gmail.com> wrote:
> On Wed, Sep 12, 2012 at 10:38 AM, Dave S <snide...@gmail.com> wrote:
>> Having tripped over THG issue 2140 (now marked as a duplicate of
>> 2090), I think it may be worthwhile to remind users here that you made
>> need to update some of your extensions (or at least disable them while
>> waiting for upgrades) to use the latest Mercurial and Tortoises. In
>> my case, it was hg subversion. If you're using just the bundled
>> extensions, this may not apply to you.
>>
> Would it be appropriate for installer packages to give you warnings to
> check your unbundled extensions when you're updating?

My thinking there, such as it was, was that said installers would be
able to test for the presence of unbundled extensions, and use that to
cue the warning.
Reply all
Reply to author
Forward
0 new messages