Classes on the stack trace (was: getElementClass/StackTraceElement, was: @CallerSensitive public API, was: sun.reflect.Reflection.getCallerClass)
Alan.Bateman at oracle.com
Fri Aug 2 22:52:57 UTC 2013
On 02/08/2013 14:15, Nick Williams wrote:
> I have patch for a public API for this just about complete. I'm going to re-run unit tests tonight and then submit it. But I need some help.
> I quickly figured out that I can't just `hg diff` from the root directory, because of the whole "forrest" thing. Ick.
> So, is there a specific way that I need to generate a diff to work with how y'all are using Mercurial? Or do I just need to `hg diff` in each sub-repository under the main repository and put all of the diff files somewhere?
> Some guidance on how to "properly" create a diff in this project would be appreciated. :-)
If you haven't already, then make sure to read the "How to contribute"
For the API proposal then I would suggest starting a discussion so that
you can get input and a sense for whether you will get a sponsor.
As regards publishing patches then attach hg diffs or publishing a
webrev (on a http server) for each of the changes repos should be fine.
More information about the core-libs-dev