From: "Harig, Mark A." <maharig@idirect.net>
To: "Robert Collins" <robert.collins@syncretize.net>, <cygwin@cygwin.com>
Subject: RE: New setup pre-release - feedback needed
Date: Wed, 17 Jul 2002 09:26:00 -0000 [thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E40F0FB@ex02.idirect.net> (raw)
Thanks for the response! I have a question/observation below.
>
> >
> > Here are some minor changes that might be worth making (no,
> they don't
> > identify bugs):
> >
> > 1. Move the 'emacs'-related items from 'Misc' to 'Editors' so that
> > they can be found more easily.
>
> This is a setup.ini driven item - you need to talk to whoever is
> packaging emacs for you and get them to add a categories tag.
>
Hmm. As far as I know, no one (or only setup.exe) is packaging emacs
for me. The only program that I know of that has touched setup.ini is
setup.exe. Are you saying that I need to edit setup.ini? Have I missed
some documentation?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-07-17 15:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 9:26 Harig, Mark A. [this message]
2002-07-17 9:56 ` Robert Collins
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 11:25 Harig, Mark A.
2002-07-17 10:12 Harig, Mark A.
2002-07-17 6:56 John Vincent
2002-07-16 13:18 Harig, Mark A.
2002-07-16 14:36 ` Max Bowsher
2002-07-17 3:26 ` Robert Collins
2002-07-17 11:43 ` Max Bowsher
2002-07-16 18:18 ` Robert Collins
2002-07-16 8:22 Demmer, Thomas
2002-07-16 8:41 ` Robert Collins
2002-07-13 12:21 Robert Collins
2002-07-15 22:13 ` Joerg R. Schaible
2002-07-17 3:11 ` Peter A. Castro
2002-07-17 3:24 ` Robert Collins
2002-07-18 2:42 ` Peter A. Castro
2002-07-17 11:59 ` Max Bowsher
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=BADF3C947A1BD54FBA75C70C241B0B9E40F0FB@ex02.idirect.net \
--to=maharig@idirect.net \
--cc=cygwin@cygwin.com \
--cc=robert.collins@syncretize.net \
/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).