From: Corwin Brust <corwin@bru.st>
To: Yuan Cao <yuancao85@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs in a Corporate Environment
Date: Wed, 12 Apr 2023 15:10:34 -0500 [thread overview]
Message-ID: <CAJf-WoTcmL7sC0VxN=yBwo+hwZKDX5bNVZ3NV2BgJVZUe86xGQ@mail.gmail.com> (raw)
In-Reply-To: <CA+wx7tVo2xH39Z5zTQYiyU1FKyv+QyZrXb2Nsr=tjbcTCwLEcw@mail.gmail.com>
Hi Yuan,
On Wed, Apr 12, 2023 at 2:48 PM Yuan Cao <yuancao85@gmail.com> wrote:
>
> Hello,
>
> I was wondering if anyone here has experience getting Emacs accepted into
> the approved software list in a corporate environment and is willing to
> answer a few questions or point me in the right direction.
I've done this, multiple times even :)
I'd be more than happy to share my experiences (and interested to hear
about others'). You are contact me off-list, if you wish, but I
suggest we should keep the conversation on-list given it is all the
same to you.
next prev parent reply other threads:[~2023-04-12 20:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:48 Emacs in a Corporate Environment Yuan Cao
2023-04-12 20:10 ` Corwin Brust [this message]
2023-04-12 20:48 ` John Yates
2023-04-12 21:33 ` Yuan Cao
2023-04-13 0:08 ` Corwin Brust
2023-04-13 14:35 ` Marcin Borkowski
2023-04-14 14:36 ` Michael Albinus
2023-04-14 14:52 ` Eli Zaretskii
2023-04-14 15:08 ` Óscar Fuentes
2023-04-14 15:47 ` Eli Zaretskii
2023-04-14 16:11 ` tomas
2023-04-15 6:12 ` Marcin Borkowski
2023-04-15 7:31 ` tomas
2023-04-15 9:12 ` Marcin Borkowski
2023-04-15 6:11 ` Marcin Borkowski
2023-04-15 7:17 ` Eli Zaretskii
2023-04-15 7:34 ` tomas
2023-04-15 7:59 ` Eli Zaretskii
2023-04-15 8:21 ` tomas
2023-04-15 9:41 ` Eli Zaretskii
2023-04-15 11:16 ` Po Lu
2023-04-15 12:04 ` Marcin Borkowski
2023-04-15 12:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-04-15 13:22 ` tomas
2023-04-15 18:45 ` Michael Albinus
2023-04-15 6:10 ` Marcin Borkowski
2023-04-15 21:14 ` Björn Bidar
2023-04-16 7:51 ` Michael Albinus
2023-04-13 14:23 ` Marcin Borkowski
2023-04-13 17:23 ` Yuan Cao
2023-04-12 20:52 ` Jean Louis
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='CAJf-WoTcmL7sC0VxN=yBwo+hwZKDX5bNVZ3NV2BgJVZUe86xGQ@mail.gmail.com' \
--to=corwin@bru.st \
--cc=help-gnu-emacs@gnu.org \
--cc=yuancao85@gmail.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).