summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormonsta <[email protected]>2016-06-10 16:46:39 +0300
committermonsta <[email protected]>2016-06-10 16:46:39 +0300
commit4e00171156b92654b7f509e0016a21654e98b3a6 (patch)
tree9a8f702a99f00fd7964c96bb23b33eb0532e6faf
parent5cf11b7ee50c491b21e5c6196a6984fcf75cb682 (diff)
downloadpluma-4e00171156b92654b7f509e0016a21654e98b3a6.tar.bz2
pluma-4e00171156b92654b7f509e0016a21654e98b3a6.tar.xz
remove one more ancient file, don't mention removed stuff in Makefile
-rw-r--r--HACKING57
-rw-r--r--Makefile.am2
2 files changed, 0 insertions, 59 deletions
diff --git a/HACKING b/HACKING
deleted file mode 100644
index 049d1ade..00000000
--- a/HACKING
+++ /dev/null
@@ -1,57 +0,0 @@
-guidelines for pluma
-====================
-
-pluma source code is maintained using the git version control system
-and is available at the following location:
-
- https://github.com/mate-desktop/pluma
-
-Please don't commit directly to the git repository unless
-you have been given the green light to commit freely to pluma.
-When in doubt assume you haven't ;-).
-
-Please attach patches in GitHub.
-If the patch fixes a bug that is not reported yet or is
-an enhancement, create a new bugreport.
-
-If you are a translator feel free to mark strings for translation,
-fix typos in the code, etc.
-
-Please send patches for build & configure fixes too. I really appreciate
-your help, I just want to review these fixes before applying.
-
-If you are a "build sheriff", feel free to commit fixes for build and
-configure (please, send me an e-mail with the patch you have applied).
-
-When committing to the pluma git repository make sure to include a
-meaningful commit message. Changes without a sufficient commit message
-will be reverted. Commit messages should have the following format:
-
-=== begin example commit ===
-Short explanation of the commit
-
-Longer explanation explaining exactly what's changed, whether any
-external or private interfaces changed, what bugs were fixed (with bug
-tracker reference if applicable) and so forth. Be concise but not too brief.
-=== end example commit ===
-
- - Always add a brief description of the commit to the _first_ line of
- the commit and terminate by two newlines (it will work without the
- second newline, but that is not nice for the interfaces).
-
- - First line (the brief description) must only be one sentence and
- should start with a capital letter unless it starts with a lowercase
- symbol or identifier. Don't use a trailing period either. Don't exceed
- 72 characters.
-
- - The main description (the body) is normal prose and should use normal
- punctuation and capital letters where appropriate. Normally, for patches
- sent to a mailing list it's copied from there.
-
- - When committing code on behalf of others use the --author option, e.g.
- git commit -a --author "Joe Coder <[email protected]>" and --signoff.
-
-
-Thanks,
-
- The pluma team.
diff --git a/Makefile.am b/Makefile.am
index 802d857c..28e0a1f8 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -12,9 +12,7 @@ distuninstallcheck_listfiles = find . -type f -print
EXTRA_DIST = \
autogen.sh \
ChangeLog \
- HACKING \
NEWS \
- NEWS.GNOME \
README \
xmldocs.make \
omf.make \