Mikhail,
Thanks a lot for review! AFAIU I need to modify the source tree [1.
DRLVM SOURCE TREE CONTENTS], am I right? Should I add 3 different GC
folders on the top level after build, for example?
EXTRACT_DIR/trunk/
|
+---build - Files required to build the
Sveta,
Yes.
IMO we have to say at least a few words for every top level directory we
have.
The dirs we have today are:
ls
MMTk
doc
em
gc_cc
gc_gen
gcv4
include
interpreter
jitrino
launcher
port
tests
thread
vmcore
vmi
vmstart
These items are missed in your version:
gc_cc - The Stop-the-world
Mikhail,
Thanks a lot for your quick response!
I'll create a new patch taking into consideration your comments.
Cheers,
Sveta
-Original Message-
From: Mikhail Fursov [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 12, 2006 1:33 PM
To: harmony-dev@incubator.apache.org
Folks,
I took a close look at the README file and Quick Help pages for users [1] and
developers [2] and created patches for these three docs [JIRA 1730]
https://issues.apache.org/jira/browse/HARMONY-1730 Taking into
consideration latest changes, I fixed duplication of info and
Sveta,
I looked through the README doc. The latest patch looks significantly better
then the first one.
The only item is missed is that we have 3 different GC folders today on the
top level.
On 10/11/06, Konovalova, Svetlana [EMAIL PROTECTED] wrote:
Folks,
I took a close look at the
Thank you for your message - Id been round 10 times before I received it. ;)
Fedotov, Alexei A wrote:
BTW,
I really enjoyed the last item of the Quick Start section:
7. If building the DRLVM fails, read this README and follow building
instructions to the point.
A hardcore
Thanks for the fix, Alexei. I think this is a good start for updating the
README.
I've looked at the current version, and many other things are out-of-date (such
as ij as the name of our executable). Some things are also duplicated - we now
have the nice Quick Help pages for users [1] and
I was looking at the patch, and think we should just chuck the whole
README.txt, salvage what's good, put it on the website, and put a
pointer in the README.txt to the website.
geir
Morozova, Nadezhda wrote:
Thanks for the fix, Alexei. I think this is a good start for updating the
README.
+1
PS: we have a pointer to README, but it goes into SVN. I don't see anything
wrong with that - there should be some docs with sources.
Best regards,
Nadya Morozova
-Original Message-
From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
Sent: Friday, October 06, 2006 1:18 PM
To:
Dear all,
Please go to https://issues.apache.org/jira/browse/HARMONY-1631 to find a
patch for README.txt. Could you please find a chance to check whether the
information is up-to date?
(pay special attention to KNOWN ISSUES and TODO sections)
In this connection I'd like to ask you to:
1.
Nadya, here is my 2 cents:
On 10/6/06, Morozova, Nadezhda [EMAIL PROTECTED] wrote:
Dear all,
Please go to https://issues.apache.org/jira/browse/HARMONY-1631 to find a
patch for README.txt. Could you please find a chance to check whether the
information is up-to date?
(pay special attention
Why don't we just add this info to the getting started pages on the
website?It's somewhat repetitive and we should just maintain in one
place.
Morozova, Nadezhda wrote:
Dear all,
Please go to https://issues.apache.org/jira/browse/HARMONY-1631 to find a
patch for README.txt. Could you
I like the README.txt file from the classlib . It helped me a lot when I
built classlib first time, so let's keep README for DRLVM too.
But classlib's README file is 2 times shorter than DRLVM's version - so it's
easier to read it.
I vote to leave in README file only info needed for a successful
There's a maintenance issue here. The point of the quickstart guides is
just that - to help someone build for the first time...
Mikhail Fursov wrote:
I like the README.txt file from the classlib . It helped me a lot when I
built classlib first time, so let's keep README for DRLVM too.
But
BTW,
I really enjoyed the last item of the Quick Start section:
7. If building the DRLVM fails, read this README and follow building
instructions to the point.
A hardcore programmer can loop infinitely here. :-)
With best regards,
Alexei Fedotov,
Intel Middleware Products Division
Yes. It's a test.
Fedotov, Alexei A wrote:
BTW,
I really enjoyed the last item of the Quick Start section:
7. If building the DRLVM fails, read this README and follow building
instructions to the point.
A hardcore programmer can loop infinitely here. :-)
With best regards,
16 matches
Mail list logo
