public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Thomas Zander <zander@javalobby.org>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve patches.
Date: Wed, 14 Apr 2004 09:56:00 -0000	[thread overview]
Message-ID: <16509.2724.862124.386156@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <200404132058.37587.zander@javalobby.org>

Thomas Zander writes:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > On Tuesday 13 April 2004 19:44, Andrew Haley wrote:
 > > I have attached a version here, FYI.
 > >
 > > I don't think I've broken anything with the checkin, but please check.
 > 
 > Hmm; I'm wondering what was wrong with the last patch I sent; the only 
 > difference I see is that I failed to mention the new method in 
 > SimpleTestHarness, and the change in statics in 
 > SimpleDateFormat/attribute.java.

This is what you sent:

diff -U3 -p -N -r mauve-orig/ChangeLog mauve/ChangeLog
--- mauve-orig/ChangeLog        2004-04-03 17:59:25.000000000 +0200
+++ mauve/ChangeLog     2004-04-03 17:54:08.000000000 +0200
@@ -1,4 +1,17 @@
+2004-04-03  Thomas Zander <zander@kde.org>
+
+       * new files
+       gnu/testlet/javax/swing/JLabel/Icon.java,
+       gnu/testlet/javax/swing/JLabel/Mnemonic.java
+
+2004-04-03  Thomas Zander <zander@kde.org>
+
+       * added an ant build option so the autotools are not needed if you use
+       a fully functional JVM (for example for writing tests).
+       build.xml:  ant build file
+       gnu/anttask/RunTests.java: ant task for calling SimpleTestHarness.java
+

This is what I did to make it right:

2004-04-13  Thomas Zander <zander@kde.org>

        * build.xml: New file.
        * gnu/anttask/RunTests.java: New file.
        * gnu/testlet/SimpleTestHarness.java (getFailures): New method.

        * gnu/testlet/javax/swing/JLabel/Icon.java: New file.
        * gnu/testlet/javax/swing/JLabel/Mnemonic.java: New file.

        * gnu/testlet/java/text/SimpleDateFormat/attribute.java 
        (test_FieldPos): Locals no longer static.

See http://www.gnu.org/prep/standards_42.html#SEC42. 

Note in particular that Change Logs document only what, not why.
Explanations should be comments in the program.

 > Was it a bad choice to sent it as a bzip2 compressed patch?

Not always, but it does mean that reviewers are less likely to look at
your patch straight away.

 > Anyway; you forgot this thingy:
 > 
 > diff -U3 -p -N -r mauve-orig/.cvsignore mauve-new/.cvsignore

Ah, yes.  Thanks.

Andrew.

  reply	other threads:[~2004-04-14  9:56 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 [this message]
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=16509.2724.862124.386156@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).