|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| backend/ | H | 20-Nov-2021 | - | 26,758 | 20,142 |
| build-aux/ | H | 20-Nov-2021 | - | 315 | 308 |
| cut-n-paste/ | H | 20-Nov-2021 | - | 19,418 | 14,898 |
| data/ | H | 03-May-2022 | - | 443 | 388 |
| help/ | H | 20-Nov-2021 | - | 131,269 | 111,749 |
| libdocument/ | H | 20-Nov-2021 | - | 14,245 | 9,167 |
| libmisc/ | H | 20-Nov-2021 | - | 1,413 | 1,056 |
| libview/ | H | 20-Nov-2021 | - | 27,914 | 21,189 |
| po/ | H | 20-Nov-2021 | - | 200,256 | 154,992 |
| previewer/ | H | 20-Nov-2021 | - | 1,317 | 968 |
| properties/ | H | 20-Nov-2021 | - | 732 | 532 |
| shell/ | H | 20-Nov-2021 | - | 26,079 | 19,684 |
| subprojects/ | H | 20-Nov-2021 | - | 6 | 5 |
| thumbnailer/ | H | 20-Nov-2021 | - | 367 | 273 |
| .editorconfig | H A D | 20-Nov-2021 | 645 | 41 | 31 |
| AUTHORS | H A D | 20-Nov-2021 | 368 | 13 | 10 |
| CONTRIBUTING.md | H A D | 20-Nov-2021 | 6 KiB | 193 | 148 |
| COPYING | H A D | 20-Nov-2021 | 17.6 KiB | 341 | 281 |
| ChangeLog.pre-git | H A D | 20-Nov-2021 | 496.8 KiB | 16,022 | 11,131 |
| MAINTAINERS | H A D | 20-Nov-2021 | 185 | 12 | 9 |
| NEWS | H A D | 20-Nov-2021 | 228.5 KiB | 7,326 | 6,043 |
| NEWS-security.md | H A D | 20-Nov-2021 | 558 | 24 | 15 |
| NOTES | H A D | 20-Nov-2021 | 2.3 KiB | 70 | 43 |
| README.commits | H A D | 20-Nov-2021 | 2.9 KiB | 69 | 51 |
| README.md | H A D | 20-Nov-2021 | 1.4 KiB | 36 | 28 |
| TODO | H A D | 20-Nov-2021 | 103 | 4 | 2 |
| evince-document.h | H A D | 20-Nov-2021 | 2.4 KiB | 64 | 41 |
| evince-view.h | H A D | 20-Nov-2021 | 1.2 KiB | 35 | 12 |
| evince.doap | H A D | 20-Nov-2021 | 2.1 KiB | 46 | 44 |
| lib-symbol.map | H A D | 20-Nov-2021 | 53 | 7 | 6 |
| meson.build | H A D | 20-Nov-2021 | 18.1 KiB | 548 | 459 |
| meson_post_install.py | H A D | 03-May-2022 | 432 | 16 | 10 |
| org.gnome.Evince.appdata.xml.in | H A D | 20-Nov-2021 | 14.2 KiB | 259 | 242 |
README.commits
1Evince is part of the GNOME git repository. At the current time, any
2person with write access to the GNOME repository, can make changes to
3Evince. This is a good thing, in that it encourages many people to work
4on Evince, and progress can be made quickly. However, we'd like to ask
5people committing to Evince to follow a few rules:
6
70) Ask first. If your changes are major, or could possibly break existing
8 code, you should always ask. If your change is minor and you've
9 been working on Evince for a while it probably isn't necessary
10 to ask. But when in doubt, ask. Even if your change is correct,
11 somebody may know a better way to do things.
12
13 If you are making changes to Evince, you should be subscribed
14 to evince-list@gnome.org. (Subscription address:
15 evince-list-request@gnome.org.) This is a good place to ask
16 about intended changes.
17
18 #evince on GIMPNet (irc.gimp.org, irc.us.gimp.org, irc.eu.gimp.org, ...)
19 is also a good place to find Evince developers to discuss changes with.
20
211) Ask _first_.
22
232) With git, we no longer maintain a ChangeLog file, but you are expected
24 to produce a meaningful commit message. Changes without a sufficient
25 commit message will be reverted. See below for the expected format
26 of commit messages.
27
283) Try to separate each change into multiple small commits that are
29 independent ("micro commits" in git speak). This way its easier to
30 see what each change does, making it easier to review, to cherry pick
31 to other branches, to revert, and to bisect.
32
33Notes:
34
35* When developing larger features or complicated bug fixes, it is
36 advisable to work in a branch in your own cloned Evince repository.
37 You may even consider making your repository publically available
38 so that others can easily test and review your changes.
39
40* The expected format for git commit messages is as follows:
41
42=== begin example commit ===
43Short explanation of the commit
44
45Longer explanation explaining exactly what's changed, whether any
46external or private interfaces changed, what bugs were fixed (with bug
47tracker reference if applicable) and so forth. Be concise but not too brief.
48=== end example commit ===
49
50 - Always add a brief description of the commit to the _first_ line of
51 the commit and terminate by two newlines (it will work without the
52 second newline, but that is not nice for the interfaces).
53
54 - First line (the brief description) must only be one sentence and
55 should start with a capital letter unless it starts with a lowercase
56 symbol or identifier. Don't use a trailing period either. Don't exceed
57 72 characters.
58
59 - The main description (the body) is normal prose and should use normal
60 punctuation and capital letters where appropriate. Normally, for patches
61 sent to a mailing list it's copied from there.
62
63 - When committing code on behalf of others use the --author option, e.g.
64 git commit -a --author "Joe Coder <joe@coder.org>" and --signoff.
65
66
67Alexander Larsson
6817 Apr 2009
69
