@@ -282,12 +282,13 @@ If you would like to contribute to the SDK, go here for more information:
282
282
283
283
### Support
284
284
285
- 1 . You will be granted support if you or your company are already covered
286
- under an existing maintenance/support agreement. Send an email to
287
- [email protected] _ and include "Splunk SDK for Python" in the subject line.
285
+ 1 . You will be granted support if you or your company are already covered
286
+ under an existing maintenance/support agreement.
287
+ Send an email to
[email protected] and include "Splunk SDK for Python"
288
+ in the subject line.
288
289
2 . If you are not covered under an existing maintenance/support agreement, you
289
290
can find help through the broader community at:
290
- <ul >
291
+ <ul >
291
292
<li ><a href =' http://splunk-base.splunk.com/answers/ ' >Splunk Answers</a > (use
292
293
the <b >sdk</b >, <b >java</b >, <b >python</b >, and <b >javascript</b > tags to
293
294
identify your questions)</li >
@@ -298,9 +299,8 @@ If you would like to contribute to the SDK, go here for more information:
298
299
code in the <b >/splunklib</b > directory) has been modified. If you modify an
299
300
SDK and want support, you can find help through the broader community and
300
301
Splunk answers (see above). We would also like to know why you modified the
301
- core library
&mdash ; please send feedback to
_ [email protected] _ .
302
- 4 . File any issues on
303
- [ GitHub] ( https://github.com/splunk/splunk-sdk-python/issues ) .
302
+ core library
&mdash ; please send feedback to
[email protected] .
303
+ 4 . File any issues on [ GitHub] ( https://github.com/splunk/splunk-sdk-python/issues ) .
304
304
305
305
### Contact Us
306
306
0 commit comments