public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Thomas Zander <zander@javalobby.org>
Cc: GNU Classpath <classpath@gnu.org>, mauve-discuss@sources.redhat.com
Subject: Re: Mauve patches.
Date: Thu, 15 Apr 2004 21:10:00 -0000	[thread overview]
Message-ID: <1082063426.1986.14.camel@elsschot.wildebeest.org> (raw)
In-Reply-To: <200404110848.06673.zander@javalobby.org>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

Hi Thomas,

On Sun, 2004-04-11 at 08:48, Thomas Zander wrote:
> Oh; and a explanation of the correct changelog format; or a link to that 
> since you said there was something wrong with it; but I don't know what.

Look at the new and improved GNU Classpath Hackers Guide:
(7.1 Documenting what changed when with ChangeLog entries)
http://www.gnu.org/software/classpath/docs/hacking.html#SEC9

> Hope to hear from you; Mauve is growing way too slow for my taste this way.

My apologies for not following up on this sooner.
I am happy that Andrew helped you out.

Your help is really appreciated. Especially since we are all short on
time. So, please don't see the slow reactions as rejections of your
work. I am really, really happy you want to pick this up and make it
easier for others. Mauve is very important but indeed far to difficult
to setup and hack on.

Thanks,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-04-15 21:10 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
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 [this message]

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=1082063426.1986.14.camel@elsschot.wildebeest.org \
    --to=mark@klomp.org \
    --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).