Fork of gtk+ with endless customizations and translations
Switch branches/tags
Clone or download
ramcq Merge pull request #85 from endlessm/T23779
theme: fix text readability on unfocused Chrome/Chromium tabs
Latest commit d1a7e47 Sep 12, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitlab-ci Disable SELinux for the container Mar 13, 2018
build Comment out VS 2011/2012 project build Apr 2, 2018
demos demo: Add widgetbowl demo Mar 15, 2018
docs gdk/wayland: Add GdkDisplay call to query available globals Feb 14, 2018
examples examples/drawing: Don't call gtk_main_quit May 22, 2017
gdk display: Add new virtual gdk_display_get_startup_notification_id() me… Jun 11, 2018
gtk theme: fix text readability on unfocused Chrome/Chromium tabs Sep 11, 2018
libgail-util MSVC Builds: Massive Rename of Projects Sep 15, 2015
m4 Add ignore file for macro dir Aug 3, 2016
m4macros m4macros: Use PKG_PROG_PKG_CONFIG Mar 26, 2018
modules Disable VIQR IM for vi locale Apr 2, 2018
po-properties Update Serbian translation Mar 28, 2018
po Update Dutch translation Mar 29, 2018
tests tests: Fix build with external file Apr 4, 2018
testsuite TMP: Remove broken reftests Apr 2, 2018
.gitlab-ci.yml Add gitlab-ci support using a prebuilt docker image Mar 4, 2018
AUTHORS small update Mar 24, 2006
COPYING Change FSF Address Feb 27, 2012
HACKING docs: Fix some old URLs Jan 9, 2015 Cosmetic formatting fixes Dec 1, 2014
MAINTAINERS update file format Aug 8, 2007 Remove config.rpath from EXTRA_DIST Aug 9, 2016
Makefile.decl build: Set no_undefined in Makefile.decl Sep 15, 2014
NEWS 3.22.29 Mar 13, 2018
NEWS.pre-1-0 ooops, fogot this on my last commit... May 7, 1998
README.commits Update README files to refer to git Mar 31, 2009 README: Refer to release notes online May 31, 2016
README.win32 docs: Fix some old URLs Jan 9, 2015
acinclude.m4 Copy newer versions of JH_CHECK_XML_CATALOG and JH_PATH_XML_CATALOG from Aug 10, 2003 TMP: Remove broken reftests Apr 2, 2018 GTK: Fix build for pre-C99 compilers May 10, 2016 gdk/x11: Add conditional support for EGL-X11 Apr 2, 2018 Bump the version to 3.0.0 Feb 10, 2011 Try to fix linking Dec 6, 2011 Add config.rpath to the list of ignored files Aug 9, 2016 Move pangoft2 to Requires.private Nov 22, 2011 Support multiple GDK backends in one build Jan 3, 2011
gtk+.doap doap category core Jul 30, 2014 Drop gdk-pixbuf files Jun 27, 2010
make-pot make-pot: Document variables Mar 3, 2015
makefile.msc win32: update msvc build Jan 2, 2011 Some people use a hacked libtool that doesn't even install .la files Apr 12, 2010


GTK+ is part of the GNOME git repository. At the current time, any
person with write access to the GNOME repository, can make changes to
GTK+. This is a good thing, in that it encourages many people to work
on GTK+, and progress can be made quickly. However, GTK+ is a fairly
large and complicated package that many other things depend on, so to
avoid unnecessary breakage, and to take advantage of the knowledge
about GTK+ that has been built up over the years, we'd like to ask
people committing to GTK+ to follow a few rules:

0) Ask first. If your changes are major, or could possibly break existing
   code, you should always ask. If your change is minor and you've
   been working on GTK+ for a while it probably isn't necessary
   to ask. But when in doubt, ask. Even if your change is correct,
   somebody may know a better way to do things.

   If you are making changes to GTK+, you should be subscribed
   to (Subscription address: This is a good place to ask
   about intended changes.

   #gtk+ on GIMPNet (,,, ...)
   is also a good place to find GTK+ developers to discuss changes with,
   however, email to gtk-devel-list is the most certain and preferred

1) Ask _first_.

2) With git, we no longer maintain a ChangeLog file, but you are expected
   to produce a meaningful commit message. Changes without a sufficient
   commit message will be reverted. See below for the expected format
   of commit messages.


* When developing larger features or complicated bug fixes, it is
  advisable to work in a branch in your own cloned GTK+ repository.
  You may even consider making your repository publically available
  so that others can easily test and review your changes.

* The expected format for git commit messages is as follows:

=== 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 <>" and --signoff.

Owen Taylor
13 Aug 1998
17 Apr 2001

Matthias Clasen
31 Mar 2009