From: Joel Reicher <joel.reicher@gmail.com>
To: Corwin Brust <corwin@bru.st>
Cc: Eli Zaretskii <eliz@gnu.org>, Elijah G <eg642616@gmail.com>,
emacs-devel@gnu.org
Subject: Re: How to contribute to Emacs Windows(NT) installer?
Date: Sat, 13 Jul 2024 15:57:12 +1000 [thread overview]
Message-ID: <86wmlpx29z.fsf@gmail.com> (raw)
In-Reply-To: <CAJf-WoTwcK7UzLEJpuDRXUPUraacbPsP2C_Xt6qVzZnTwo9Dpw@mail.gmail.com> (Corwin Brust's message of "Fri, 12 Jul 2024 07:39:47 -0500")
Corwin Brust <corwin@bru.st> writes:
> On Fri, Jul 12, 2024 at 5:07 AM Joel Reicher
> <joel.reicher@gmail.com> wrote:
>>
>> Corwin Brust <corwin@bru.st> writes:
>>
>>> I have lots and lots of rather so-so code relating to making
>>> these builds, most of which I don't use when preparing release
>>> builds which I do rather manually.
>>
>> Do you have those manual steps documented, even roughly?
>
> Not outstandingly well, certainly. Here is the talk I gave at
> EmacsConf last year:
>
> https://emacsconf.org/2023/talks/windows/
Thanks; that made sense. Two questions:
1) Is there anything you would like help with at the moment? A
particular bug or two? (You mention some in the talk but that was
6 months ago.)
2) How do you provision/construct your build environment? In the
talk I think you allude to it but never really describe it.
Regards,
- Joel
next prev parent reply other threads:[~2024-07-13 5:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 2:42 How to contribute to Emacs Windows(NT) installer? Elijah G
2024-04-20 6:22 ` Eli Zaretskii
2024-04-21 22:00 ` Corwin Brust
2024-04-21 22:38 ` Elijah G
2024-04-22 0:04 ` Elijah G
2024-04-22 2:13 ` Corwin Brust
2024-04-23 1:45 ` Elijah G
2024-04-23 15:35 ` Corwin Brust
2024-04-23 15:43 ` Elijah G
2024-07-12 10:07 ` Joel Reicher
2024-07-12 12:39 ` Corwin Brust
2024-07-13 5:57 ` Joel Reicher [this message]
2024-07-13 10:35 ` Corwin Brust
2024-07-13 16:26 ` Michael Albinus
2024-07-13 17:10 ` Joel Reicher
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wmlpx29z.fsf@gmail.com \
--to=joel.reicher@gmail.com \
--cc=corwin@bru.st \
--cc=eg642616@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).