From the 'Contributing your work' section of
http://wiki.apache.org/lucene-hadoop/HowToContribute:
"Should your patch earn a -1 on the Hudson test, set the issue status to
'Resume Progress', upload a patch with necessary fixes and then set the
status to 'Submit Patch' again."
Let us know if the cited section is unclear or needs improvement so it
can be fixed.
Yours,
St.Ack
Christophe Taton wrote:
Ok, I remade my patch following the howto carefully. I removed the previous
patch and attached a new one.
I am a bit confused now, is it ok or should I cancel and submit again?
Thanks.
On 7/26/07, Nigel Daley <[EMAIL PROTECTED]> wrote:
You can find the process here:
http://wiki.apache.org/lucene-hadoop/HowToContribute
Note that the automated patch process attempts to apply the latest
patch (the one that was uploaded last) and will ignore *.htm and
*.html files.
On Jul 26, 2007, at 3:55 PM, Christophe Taton (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-1653?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Taton updated HADOOP-1653:
-------------------------------------
Status: Patch Available (was: Reopened)
Sorry, just trying to figure out how the issue workflow works...
FSDirectory class code cleanup
------------------------------
Key: HADOOP-1653
URL: https://issues.apache.org/jira/browse/
HADOOP-1653
Project: Hadoop
Issue Type: Improvement
Components: dfs
Affects Versions: 0.15.0
Reporter: Christophe Taton
Priority: Trivial
Attachments: fsdirectory-cleanup-20070725-1706.patch
- lets FSDirectory.INode become a static class, thus sparing one
pointer per INode
- removes an unused constructor for FSDirectory.INode
- merges identical methods INode.getAbsoluteName() and
INode.computeName() and optimizes it using StringBuffer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
