public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason-swarelist@molenda.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: 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 00:24:00 -0000	[thread overview]
Message-ID: <20000412002350.A10419@shell17.ba.best.com> (raw)
Message-ID: <20000412002400.vLoTHCn_r455xN3RIMw2V4UnoVggbOkLLBCX37Ddw7s@z> (raw)
In-Reply-To: <38F41730.5075FD59@cygnus.com>

On Wed, Apr 12, 2000 at 04:26:56PM +1000, Andrew Cagney wrote:
> Tom Tromey wrote:

> > Who makes decisions about write access for dejagnu?
> > I have a patch I'd like to check in.

> The official dejagnu sources are on http://sourceforge .<something>.  I'd
> suggest submit the patch there and also apply the change to the local
> mostly maintenance branch.  I assume it is nothing radical.

We went over all of this on a Cygnus internal list months ago.

Rob's repository on sourceforge is nothing but our own dejagnu.
He hasn't added a single change in the fourteen months that he has
had a separate repository--he's just imported changes that have
been made at Cygnus.

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.

I would certainly not cooperate with this repository until the
Cygnus-internal, customer confidential, information, tags, and
infrastructure is completely stripped.  He essentially needs to
throw away this repository and start over.  It should not be too
difficult; as I said earlier, he hasn't done anything of substance
on his fork.

After his repository is free of confidential information, I'd still
not bother coordinating with him unless there was someone actually
doing something in that repository.  But that's more of a judgement
call.


Anyway, as for our local repository on sourceware, last I heard,
changes to dejagnu are considered a free-for-all, with possible
review or oversight by Jim Wilson (he volunteered) if someone wanted
to talk with someone about a change.

Jason

  parent reply	other threads:[~2000-04-12  0:24 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     ` Tom Tromey
2000-04-12  8:06       ` Tom Tromey
2000-12-30  6:08     ` Jason Molenda [this message]
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
2000-04-12  8:55         ` Jeffrey A Law
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=20000412002350.A10419@shell17.ba.best.com \
    --to=jason-swarelist@molenda.com \
    --cc=ac131313@cygnus.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).