public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Michael Koch <konqueror@gmx.de>
To: Thomas Zander <zander@javalobby.org>, mauve-discuss@sources.redhat.com
Cc: GNU Classpath <classpath@gnu.org>
Subject: Re: Mauve patches.
Date: Thu, 08 Apr 2004 19:50:00 -0000	[thread overview]
Message-ID: <200404082150.24907.konqueror@gmx.de> (raw)
In-Reply-To: <200404082133.32680.zander@javalobby.org>

Am Donnerstag, 8. April 2004 21:33 schrieb Thomas Zander:
> I'd really like to see my stuff committed, or commented on if just
> committing is unacceptable.
>
> Are there any people actually maintaining mauve?  Nobody commented on
> the fixed needed for the website either.
> In short who is the core maintainer for mauve?

Mauve has no real maintainer. There are just some people that commit 
stuff in a chaotic way.

Michael

> On Tuesday 06 April 2004 10:46, Michael Koch wrote:
> > Am Dienstag, 6. April 2004 09:56 schrieb Thomas:
> > > I've submitted several patches to both list and hear nothing; is
> > > there anyone who can comment/commit on these?
> >
> > We are all doing this in our freetime so we need some time nee out
> > backlogs sometimes.
> >
> > Personally I have Mauve CVS access but I'm using not using ant so I
> > cant really vote on your patch. I think Tom Tromey or Mark Wielaard
> > will look into this in some days. If not please ping me and I will
> > do it.
> >
> >
> > Michael

  reply	other threads:[~2004-04-08 19:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  7:55 Thomas
2004-04-06  8:47 ` Michael Koch
2004-04-08 19:34   ` Thomas Zander
2004-04-08 19:50     ` Michael Koch [this message]
2004-04-08 19:58       ` Andrew Haley
2004-04-11  6:48         ` Thomas Zander
2004-04-11 12:22           ` David Lichteblau
2004-04-11 17:20             ` Thomas Zander
2004-04-11 18:57               ` David Lichteblau
2004-04-11 19:37                 ` Thomas Zander
2004-04-12  4:12                   ` C. Brian Jones
2004-04-16 20:23                     ` Anthony Green
2004-04-16 22:57                       ` C. Brian Jones
2004-04-13 13:22                 ` Andrew Haley
2004-04-13 13:55                   ` Thomas
2004-04-13 14:30                     ` Andrew Haley
2004-04-13 17:14                       ` Thomas Zander
2004-04-13 17:45                         ` Andrew Haley
2004-04-13 18:59                           ` Thomas Zander
2004-04-14  9:56                             ` Andrew Haley
2004-04-14  0:09                     ` Bill McFadden
2004-04-15 22:56                 ` Mark Wielaard
2004-04-17 14:45                   ` Thomas Zander
2004-04-11 15:56           ` Archie Cobbs
2004-04-15 21:10           ` Mark Wielaard

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=200404082150.24907.konqueror@gmx.de \
    --to=konqueror@gmx.de \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=zander@javalobby.org \
    /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).