[Trilinos-Users] Patch submission process

[Carlos Reyes]

The standard method on GitHub to submit patches to a project is by using 
a pull request. General documentation on the subject can be found here:

https://help.github.com/categories/collaborating-on-projects-using-issues-and-pull-requests/

You can find a list of the pull requests for Trilinos awaiting 
processing here:

https://github.com/trilinos/Trilinos/pulls

Individual projects often have an additional set of requirements before 
they will consider incorporating the code patches contained in a pull 
request. I did not see a specific set of guidelines for Trilinos, but it 
won't hurt to familiarize yourself with the project policies:

https://github.com/trilinos/Trilinos/wiki/POLICIES

Carlos Reyes
1-505-206-1569 (mobile)

On 08/25/2016 10:07 AM, Roberts, Nathan V. wrote:
> Hello all,
>
> Before the transition to the GitHub repo, there was a documented process for submitting patches.  A couple patches I submitted this way seem to have gotten lost in the transition.  So, I'd like to resubmit these, as well as a couple new ones.
>
> Is the process for submitting patches to the GitHub repo documented somewhere?
>
> Thanks,
> Nate
> _______________________________________________
> Trilinos-Users mailing list
> Trilinos-Users at trilinos.org
> https://trilinos.org/mailman/listinfo/trilinos-users


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4343 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://trilinos.org/pipermail/trilinos-users/attachments/20160826/bf00f068/attachment.p7s>