From: Jeffrey A Law <law@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Tom Tromey <tromey@cygnus.com>,
overseers <overseers@sourceware.cygnus.com>,
Jim Blandy <jimb@cygnus.com>,
krk@cygnus.com, wilson@cygnus.com
Subject: Re: dejagnu group
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <16259.955550784@upchuck> (raw)
In-Reply-To: <20000412002350.A10419@shell17.ba.best.com>
In message < 20000412002350.A10419@shell17.ba.best.com >you write:
> More importantly, Rob's repository is _still_ an unsanitized tree
> that he copied from Cygnus when he left. A Cygnus person should
> get on bmoss/krk to get this resolved -- both bmoss and krk said
> they would follow up with it quickly, but nothing has changed on
> the sourceforge repo. The repository, as is, is not acceptable
> for public consumption. If nothing else, contact VA and get this
> project pulled.
What needs to happen is for someone from Cygnus to review the code and
find any unsanitary bits.
Rob has pulled bits that I pointed out were still secret -- that was
before the repo went up on sourceforge -- at least he said he pulled
the secret bits, I haven't actually followed up and checked.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Tom Tromey <tromey@cygnus.com>,
overseers <overseers@sourceware.cygnus.com>,
Jim Blandy <jimb@cygnus.com>,
krk@cygnus.com, wilson@cygnus.com
Subject: Re: dejagnu group
Date: Wed, 12 Apr 2000 08:55:00 -0000 [thread overview]
Message-ID: <16259.955550784@upchuck> (raw)
Message-ID: <20000412085500.bbKzF5o2vAi9_UK-gCvPbxi6ZLxmDHfGeFnzqetgWH8@z> (raw)
In-Reply-To: <20000412002350.A10419@shell17.ba.best.com>
In message < 20000412002350.A10419@shell17.ba.best.com >you write:
> More importantly, Rob's repository is _still_ an unsanitized tree
> that he copied from Cygnus when he left. A Cygnus person should
> get on bmoss/krk to get this resolved -- both bmoss and krk said
> they would follow up with it quickly, but nothing has changed on
> the sourceforge repo. The repository, as is, is not acceptable
> for public consumption. If nothing else, contact VA and get this
> project pulled.
What needs to happen is for someone from Cygnus to review the code and
find any unsanitary bits.
Rob has pulled bits that I pointed out were still secret -- that was
before the repo went up on sourceforge -- at least he said he pulled
the secret bits, I haven't actually followed up and checked.
jeff
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Andrew Cagney
2000-04-11 23:03 ` Andrew Cagney
2000-12-30 6:08 ` Jeffrey A Law
2000-04-11 23:19 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-04-11 23:13 ` Tom Tromey
2000-12-30 6:08 ` Andrew Cagney
2000-04-11 23:28 ` Andrew Cagney
2000-12-30 6:08 ` Jason Molenda
2000-04-12 0:24 ` Jason Molenda
2000-12-30 6:08 ` Jim Kingdon
2000-04-12 5:31 ` Jim Kingdon
2000-12-30 6:08 ` Kim Knuttila
2000-04-12 6:53 ` Kim Knuttila
2000-12-30 6:08 ` Jeffrey A Law [this message]
2000-04-12 8:55 ` Jeffrey A Law
2000-12-30 6:08 ` Tom Tromey
2000-04-12 8:06 ` Tom Tromey
2000-12-30 6:08 ` Andrew Cagney
2000-04-11 23:26 ` 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=16259.955550784@upchuck \
--to=law@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=jimb@cygnus.com \
--cc=krk@cygnus.com \
--cc=overseers@sourceware.cygnus.com \
--cc=tromey@cygnus.com \
--cc=wilson@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).