Hi Aroon --
The traditional guidance for submitting code patches has been thin,
and located in:
trunk/doc/developer/bestPractices/Subversion.txt
But, based on your message, I've taken a pass over it, fleshed it out
significantly, and forked it into its own file, now located at:
trunk/doc/developer/bestPractices/CommittingCode.txt
My intention is to link to this to the "developers" page at
chapel.cray.com once a few more eyes have had a chance to look over it.
Let me know if you have any questions, find problems in the file, etc.
Thanks,
-Brad
On Tue, 10 Jun 2014, Aroon Sharma wrote:
Hi everyone,
My work on the modulo unrolling optimization that I presented at CHIUW
(http://chapel.cray.com/CHIUW/2014/Sharma_talk.pdf) is wrapping up, so I
wanted to know what process I would need to go through to commit my work
on the Cyclic and Block Cyclic distributions to the Chapel trunk. In
addition to my patches to CyclicDist.chpl and BlockCyclicDist.chpl, I
would also like to commit a series of Chapel benchmarks that I used to
test my work that aren't present in the trunk.
If more information is needed on how my optimization works, I'm working
on a draft of a paper to submit to PGAS that I can provide. I've never
committed to Chapel before, so please be as specific as possible when
describing this commit/review process. Thanks. Aroon Sharma University
of Maryland, Class of 2015 M.S. Computer Engineering (301) 908-9528
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
