From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Paranormal bug in TL 2016
Date: Tue, 11 Oct 2016 11:10:29 +0200 [thread overview]
Message-ID: <ca49a138-bb4e-2c0f-ddbe-e627936d2f44@gmail.com> (raw)
In-Reply-To: <CALBOmsbz2aqc3bhyvmPbNMXfRUvV0aqw5_PK3+-2_dd0f8tXww@mail.gmail.com>
On 10/10/2016 03:59 PM, Mojca Miklavec wrote:
> On 10 October 2016 at 15:31, Henri Menke wrote:
>> I have found another thread reporting the same problem
>>
>> https://www.mail-archive.com/ntg-context@ntg.nl/msg82349.html
>>
>> However, Hans only replied with »has been fixed already«.
>>
>> Does anyone know how to find the fix?
>
> Unless Hans remembers what he fixed exactly, my only idea is doing a
> bisection over
> https://bitbucket.org/phg/context-mirror/commits/all
I'm willing to bisect it but I don't know how to integrate the git repo into the standalone distribution. Are there instructions somewhere?
>
> In case you find the fix, I can "backport" it to TL's repository and
> users doing regular upgrades with tlmgr will get it at least.
>
> Mojca
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-11 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 10:14 Henri Menke
2016-10-10 10:31 ` Thomas A. Schmitz
2016-10-10 11:49 ` Henri Menke
2016-10-10 12:03 ` Thomas A. Schmitz
2016-10-10 13:31 ` Henri Menke
2016-10-10 13:59 ` Mojca Miklavec
2016-10-11 9:10 ` Henri Menke [this message]
2016-10-11 10:01 ` Henri Menke
2016-10-11 13:33 ` Henri Menke
2016-10-11 13:45 ` Mojca Miklavec
2016-10-11 13:58 ` Henri Menke
2016-10-11 14:01 ` luigi scarso
2016-10-12 6:58 ` Otared Kavian
2016-10-12 9:19 ` Henri Menke
2016-10-11 13:57 ` Arthur Reutenauer
2016-10-10 12:19 ` Ulrike Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca49a138-bb4e-2c0f-ddbe-e627936d2f44@gmail.com \
--to=henrimenke@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).