From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] New: luajit-2.0.4-1 [GOLDSTAR]
Date: Mon, 21 Sep 2015 19:03:00 -0000 [thread overview]
Message-ID: <m2l00bdnc28lagput16i2a74ud95urmi3j@4ax.com> (raw)
In-Reply-To: <1442850565.11704.1.camel@cygwin.com>
> On Sun, 2015-09-20 at 14:31 -0400, Ken Brown wrote:
> > On 9/19/2015 8:34 AM, Ken Brown wrote:
> > > On 9/18/2015 6:08 PM, Yaakov Selkowitz wrote:
> > >> On Fri, 2015-09-18 at 15:15 -0400, Ken Brown wrote:
> > >>> Thanks for this! I can use your 64-bit patch to build luajittex on
> > >>> 64-bit Cygwin. Two questions:
> > >>>
> > >>> 1. Do you plan to send your patch upstream? I had some correspondence
> > >>> with the author last year in which he said he would welcome a patch to
> > >>> make luajit build on 64-bit Cygwin.
> > >>
> > >> Unfortunately, upstreaming takes time (particularly when dealing with
> > >> the many misconceptions people have about Cygwin) so I've admittedly
> > >> been lax in that regard.
> > >
> > > I have to send the patch to upstream TeX Live anyway, so I could just
> > > copy the luajit author.
> >
> > I did this, and he just applied the patch (with credit to you) as git
> > commit 076d625.
>
> Thanks! Andrew?
Gold star awarded! https://cygwin.com/goldstars/#KB
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-09-21 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 16:48 [ANNOUNCEMENT] New: luajit-2.0.4-1 Yaakov Selkowitz
2015-09-18 19:15 ` Ken Brown
2015-09-18 22:08 ` Yaakov Selkowitz
2015-09-19 12:34 ` Ken Brown
2015-09-20 18:31 ` Ken Brown
2015-09-21 15:49 ` [ANNOUNCEMENT] New: luajit-2.0.4-1 [GOLDSTAR] Yaakov Selkowitz
2015-09-21 19:03 ` Andrew Schulman [this message]
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=m2l00bdnc28lagput16i2a74ud95urmi3j@4ax.com \
--to=schulman.andrew@epa.gov \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).