From: Stefan Kangas <stefan@marxist.se>
To: Mambo Levis <mambo.levis@gmail.com>
Cc: "ofv@wanadoo.es" <ofv@wanadoo.es>,
"a.s@realize.ch" <a.s@realize.ch>,
24574-done@debbugs.gnu.org,
"npostavs@users.sourceforge.net" <npostavs@users.sourceforge.net>
Subject: bug#24574: emacs-module is not GPL compatible (Windows)
Date: Fri, 22 Oct 2021 19:47:44 -0700 [thread overview]
Message-ID: <CADwFkm=OpBt7Sm9JDzMO1bJj7MXSZS2X_=TomBjEmK_kcktmfA@mail.gmail.com> (raw)
In-Reply-To: <1721463445.452969.1475686278575@mail.yahoo.com> (Mambo Levis's message of "Wed, 5 Oct 2016 16:51:18 +0000 (UTC)")
Mambo Levis <mambo.levis@gmail.com> writes:
> On Wednesday, October 5, 2016 4:48 AM, "npostavs@users.sourceforge.net" <npostavs@users.sourceforge.net> wrote:
[...]
>> So there is no bug after all? Should we just close this report, or is
>> there perhaps some guidance we should add to the documentation about how
>> to build modules on Windows?
[...]
> Yes, in summary there is no bug after all, yes you can close it.
Thanks, I read this thread and I can't see what we can add here besides
the usual "fiddle with paths, put stuff where it belongs".
So I'm closing this bug report.
prev parent reply other threads:[~2021-10-23 2:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1261593588.2422705.1475266631400.ref@mail.yahoo.com>
2016-09-30 20:17 ` emacs-module is not GPL compatible (Windows) Mambo Levis
2016-10-01 1:14 ` Óscar Fuentes
2016-10-01 1:21 ` Óscar Fuentes
2016-10-01 4:37 ` bug#24574: " Robert Cochran
2016-10-01 7:53 ` Alain Schneble
2016-10-01 12:31 ` Mambo Levis
2016-10-01 15:40 ` bug#24574: " Eli Zaretskii
2016-10-01 20:28 ` Mambo Levis
2016-10-02 6:24 ` Eli Zaretskii
2016-10-02 15:53 ` Mambo Levis
2016-10-05 2:48 ` npostavs
2016-10-05 16:51 ` Mambo Levis
2021-10-23 2:47 ` Stefan Kangas [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='CADwFkm=OpBt7Sm9JDzMO1bJj7MXSZS2X_=TomBjEmK_kcktmfA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=24574-done@debbugs.gnu.org \
--cc=a.s@realize.ch \
--cc=mambo.levis@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=ofv@wanadoo.es \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.