From: Fabien DUMINY <fduminy@users.sourceforge.net>
To: Michael Koch <konqueror@gmx.de>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Can I commit a bug fix in CreateTags.java ?
Date: Sat, 17 Sep 2005 12:20:00 -0000 [thread overview]
Message-ID: <432C09CC.3070402@users.sourceforge.net> (raw)
In-Reply-To: <20050917115254.GI19178@asterix.konqueror.de>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Michael Koch a écrit :
>On Sat, Sep 17, 2005 at 01:24:00PM +0200, Fabien DUMINY wrote:
>
>
>>Hi,
>>I found and fixed a bug in CreateTags. The ';' wasn't removed from the package declaration and it
>>was written in the testlet className.
>>
>>Can I commit the bug fix (when I will have the rights to do) ?
>>I ask you that question because I read that such modification (in the core of Mauve, not in the
>>testlets) should be discussed here.
>>
>>
>
>Please send a patch representing this change here.
>
>
>Michael
>
>
Here is the patch (joined file).
Fabien.
[-- Attachment #2: CreateTags_bugfix.patch --]
[-- Type: text/plain, Size: 823 bytes --]
Index: CreateTags.java
===================================================================
RCS file: /cvs/mauve/mauve/gnu/testlet/runner/CreateTags.java,v
retrieving revision 1.1
diff -u -r1.1 CreateTags.java
--- CreateTags.java 1 Jul 2005 18:33:43 -0000 1.1
+++ CreateTags.java 17 Sep 2005 12:14:22 -0000
@@ -130,7 +130,10 @@
tags = line;
}
else if(buf.indexOf("package ") == 0)
- pckage = buf.substring(8, buf.length()-1);
+ {
+ int idx = buf.lastIndexOf(";");
+ pckage = buf.substring(8, idx);
+ }
buf = new StringBuffer();
maxLines--;
}
next prev parent reply other threads:[~2005-09-17 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 11:23 Fabien DUMINY
2005-09-17 11:54 ` Michael Koch
2005-09-17 12:20 ` Fabien DUMINY [this message]
2005-09-19 12:51 ` David Gilbert
2005-09-24 8:18 ` Fabien DUMINY
2005-10-08 14:02 ` RFA: " Fabien DUMINY
2005-09-22 15:48 ` Tom Tromey
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=432C09CC.3070402@users.sourceforge.net \
--to=fduminy@users.sourceforge.net \
--cc=konqueror@gmx.de \
--cc=mauve-discuss@sources.redhat.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).