Github user kdatta commented on the pull request:
https://github.com/apache/spark/pull/4205#issuecomment-71502610
Updated to "[GRAPHX] Spark 3789 - Python Bindings for GraphX"
On Mon, Jan 26, 2015 at 9:35 AM, Mark Hamstra <[email protected]>
wrote:
> Yes, +1 to Sandy's request.
>
> In general, the JIRA should explain *why* a change is necessary or
> advisable, the description of the PR should explain *what* is being done
> to fix the problem or add the feature, and the title of the PR should
> provide a useful summary of the PR since that title will end up as the
> commit message in the git log.
>
> When these recommendation aren't followed, reviewers and other developers
> are forced to look in multiple places or even at the code in order to get
> even a basic idea of what the PR or commit is about.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/4205#issuecomment-71501211>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
