Skip to content
Snippets Groups Projects
Commit e300e2be authored by Shawn Pearce's avatar Shawn Pearce
Browse files

Update SUBMITTING_PATCHES to point to Contributor Guide


The process is likely to change as we experiment with Gerrit Code
Review and learn the Eclipse IP process.  Lets point the potential
contributor at a wiki that we can more easily keep up-to-date.

Change-Id: I99f7cb9edadd0f23024f59ec139dd1e35f5fbd3f
Signed-off-by: default avatarShawn O. Pearce <spearce@spearce.org>
parent 6828372f
No related branches found
No related tags found
No related merge requests found
...@@ -3,24 +3,15 @@ Short Version: ...@@ -3,24 +3,15 @@ Short Version:
- Make small logical changes. - Make small logical changes.
- Provide a meaningful commit message. - Provide a meaningful commit message.
- Include your Signed-Off-By line to note you agree with the - Review and follow the Eclipse Due Diligence Process
Developer's Certificate of Origin (see below).
- Make sure all code is under the proper license:
3-clause BSD http://www.eclipse.org/projects/dev_process/ip-process-in-cartoons.php
http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf
- Use a subject prefix of "[PATCH JGIT ...]" when sending any - Review and follow the current guidelines:
patches directly by email.
- Send by email to the maintainers, cc'ing the git mailing list http://wiki.eclipse.org/EGit/Contributor_Guide
which is currently used for both Git and JGit:
maintainers : "Shawn O. Pearce" <spearce@spearce.org>
Robin Rosenberg <robin.rosenberg@dewire.com>
git list : git@vger.kernel.org
git list info : http://vger.kernel.org/vger-lists.html#git
Long Version: Long Version:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment