From: Andrew Haley <aph@redhat.com>
To: Thomas Zander <zander@javalobby.org>
Cc: mauve-discuss@sources.redhat.com
Subject: Some issues..
Date: Sat, 03 Apr 2004 13:16:00 -0000 [thread overview]
Message-ID: <16494.47358.415834.600012@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <200404031504.41093.zander@javalobby.org>
Thomas Zander writes:
>
> Next CVS does not compile with suns javac
> (gnu/testlet/java/text/SimpleDateFormat/attribute.java)
Would you please help us here by sending a patch?
> Please make the project seem 'less dead' to the passing eye!! If Red-hat
> does not do anything; what about moving the project to sourceforge or
> savannah ??
How would moving the project to a different server help? Many people
contribute to Mauve, Red Hat provide the server.
> Anyway; maybe someone here can answer my question posted on the classpath
> list a couple of days ago (providing a patch to mauve).
> http://mail.gnu.org/archive/html/classpath/2004-04/msg00000.html
It was a very strange patch. A tarfile with one file that was a diff,
and a new directory. However, that patch looks reasonable enough.
However, there was no ChangeLog entry; we'll need one of those.
Andrew.
next prev parent reply other threads:[~2004-04-03 13:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:05 Thomas Zander
2004-04-03 13:16 ` Andrew Haley [this message]
2004-04-03 13:41 ` Thomas Zander
2004-04-03 15:42 ` Andrew Haley
2004-04-03 16:06 ` Thomas Zander
2004-04-15 22:22 ` Mark Wielaard
2004-04-16 9:31 ` Andrew Haley
2004-04-16 11:29 ` Mark Wielaard
2004-04-16 12:01 ` Some issues.. (batch_run and runner script documentation) Mark Wielaard
2004-04-16 12:04 ` Some issues Andrew Haley
2004-04-22 21:41 ` Mark Wielaard
2004-04-15 22:14 ` Mark Wielaard
2004-05-07 11:54 ` John Leuner
2004-05-07 13:25 ` Thomas
2004-04-23 9:12 Jeroen Frijters
2004-04-25 11:10 ` Mark Wielaard
2004-04-29 11:41 ` Andrew Haley
2004-04-29 13:16 ` Thomas
2004-04-29 15:29 ` Andrew Haley
2004-05-01 9:49 ` Thomas Zander
2004-05-02 12:27 ` Andrew Haley
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=16494.47358.415834.600012@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--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).