From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: ITP: cscope -- Interactively examine a C program source
Date: Mon, 15 Oct 2012 08:18:00 -0000 [thread overview]
Message-ID: <20121015081823.GB2110@calimero.vinschen.de> (raw)
In-Reply-To: <507B0AEF.3030705@kringlecottage.com>
Hi Dave,
Hi Jari,
On Oct 14 13:56, Dave And Diane wrote:
> Effectively yes. I'm cool with mlcscope being removed from the
> package list when cscope appears.
Three followup questions:
- Does mlcscope provide functionality cscode doesn't? That might
be a point in favor of keeping it alive, unless you think it's
not that important.
- If we obsolete mlcscope, would it make sense to create a new, empty
mlcscope package which "requires" cscope so that cscope is automatically
replacing mlcscope in existing installations?
- If so, would it also make sense if the cscope package creates a
mlcscope symlink -> cscope to help people along which use mlcsope in
scripts (if that makes any sense at all??
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2012-10-15 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 9:20 Jari Aalto
2012-10-07 13:26 ` Dave And Diane
2012-10-09 11:07 ` Corinna Vinschen
2012-10-09 11:24 ` Jari Aalto
2012-10-14 18:56 ` Dave And Diane
2012-10-15 8:18 ` Corinna Vinschen [this message]
2012-10-20 3:37 ` Dave And Diane
2012-10-20 11:22 ` Corinna Vinschen
2012-10-20 23:54 ` Dave And Diane
2012-10-21 10:18 ` Corinna Vinschen
2012-10-29 3:00 ` Dave And Diane
2012-10-29 8:50 ` Corinna Vinschen
2012-10-08 11:44 ` marco atzeri
2012-10-09 11:06 ` Corinna Vinschen
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=20121015081823.GB2110@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@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).