From: Gacquer William <William.Gacquer@laposte.net>
To: Mo DeJong <mdejong@cygnus.com>, sourcenav@sourceware.cygnus.com
Subject: Re: replace (plain text)
Date: Wed, 04 Jul 2001 13:52:00 -0000 [thread overview]
Message-ID: <01070422504300.01873@localhost.localdomain> (raw)
In-Reply-To: <Pine.SOL.3.91.1010704113153.9121B-100000@cse.cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
Just a word about the cygnus CVS tree. Do you keep it secret cos your
customers asked for custom developments that are visible in some cygnus tree
branches? ( as Sony did for its Playstation 2 SDK, for instance, but that was
a Cygnus Japan work )
Having access to the whole tree would greatly simplify a lot of things for
us.
William Gacquer
Le Mercredi 4 Juillet 2001 14:49, Mo DeJong a écrit :
> On Tue, 3 Jul 2001, Berek Half-hand wrote:
>
> ...
>
> > So...instead of talking about code base search and replace, why doesn't
> > someone at RedHat fix some of these serious problems? I haven't been able
> > to get an xref of any code base in any language (except a simple std C
> > grep I wrote years ago) for over three years. Pardon my frustration, but
> > I really wish I had my money back. Any chance of that?
>
> Frankly, I am not sure how to respond to your email. I seem to remember
> explaining options that folks had when faced with a bug on this list
> a number of times. Whining about a bug is not really the most effective
> course of action.
>
> Just because you don't see any improvement in a specific set of bugs
> does not mean that we are not fixing things. Currently, we are working
> on the Tcl/Tk 8.3 upgrade and getting CVS access setup. This work
> is much more important then the parsers. The parsers need work, it
> is a know issue and it is likely one that will never be solved to
> everyone's satisfaction (since everyone wants something different).
>
> Mo DeJong
> Red Hat Inc
next prev parent reply other threads:[~2001-07-04 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 7:02 replace Aurelian Melinte
2001-07-03 13:12 ` replace Mo DeJong
2001-07-03 13:54 ` replace Gacquer William
2001-07-03 14:45 ` replace Mo DeJong
2001-07-03 15:32 ` SN +gvim + ex-ctags == excellent free IDE Subrata Datta
2001-07-03 18:37 ` replace (plain text) Berek Half-hand
2001-07-03 22:54 ` Eric Christopher
2001-07-04 11:49 ` Mo DeJong
2001-07-04 12:09 ` Berek Half-hand
2001-07-04 15:11 ` Eric Christopher
2001-07-09 7:17 ` Aurelian Melinte
2001-07-04 13:52 ` Gacquer William [this message]
2001-07-04 14:38 ` Mo DeJong
2001-07-04 15:10 ` Gacquer William
2001-07-05 18:21 ` Mo DeJong
2001-07-06 13:41 ` Andrew Cagney
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=01070422504300.01873@localhost.localdomain \
--to=william.gacquer@laposte.net \
--cc=mdejong@cygnus.com \
--cc=sourcenav@sourceware.cygnus.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).