·
> On 7/29/2014 7:18 PM, Philipp Gesang wrote:
> > ·
> >
> >> On 7/29/2014 7:01 AM, Philipp Gesang wrote:
> >>
> >>> Thanks for the quick fix!
> >>
> >> You were just lucky that I saw it pop up as incoming mail message (which
> >> I somehow cannot turn off) because normally all ma
On 7/29/2014 7:18 PM, Philipp Gesang wrote:
·
On 7/29/2014 7:01 AM, Philipp Gesang wrote:
Thanks for the quick fix!
You were just lucky that I saw it pop up as incoming mail message (which
I somehow cannot turn off) because normally all mails directed a the
luatex list is filtered a
·
> On 7/29/2014 7:01 AM, Philipp Gesang wrote:
>
> > Thanks for the quick fix!
>
> You were just lucky that I saw it pop up as incoming mail message (which
> I somehow cannot turn off) because normally all mails directed a the
> luatex list is filtered away to its own bin as it seldom
On 7/29/2014 7:01 AM, Philipp Gesang wrote:
Thanks for the quick fix!
You were just lucky that I saw it pop up as incoming mail message (which
I somehow cannot turn off) because normally all mails directed a the
luatex list is filtered away to its own bin as it seldom relates to
context.
Good morning, Hans!
Thanks for the quick fix!
Best,
Philipp
·
> ·
>
> > (CC’ing the Context list.)
> >
> > ·
> >
> > > Do you have a prediction about how long it will take before a fix is
> > > released?
> >
> > No, sorry. What I do have though is the culprit:
> >
>
·
> (CC’ing the Context list.)
>
> ·
>
> > Do you have a prediction about how long it will take before a fix is
> > released?
>
> No, sorry. What I do have though is the culprit:
>
> c70b2e466bbb07e976f8684d56ae4e5398169e7d is the first bad commit
Seems to be related to
(CC’ing the Context list.)
·
> Do you have a prediction about how long it will take before a fix is
> released?
No, sorry. What I do have though is the culprit:
c70b2e466bbb07e976f8684d56ae4e5398169e7d is the first bad commit
commit c70b2e466bbb07e976f8684d56ae4e5398169e7d
