diff options
| author | Matthias Clasen <mclasen@redhat.com> | 2009-03-31 18:49:48 -0400 |
|---|---|---|
| committer | Matthias Clasen <mclasen@redhat.com> | 2009-03-31 19:34:23 -0400 |
| commit | 5ef4c2b9bdf6df0711b62502c2cff68be2daef54 (patch) | |
| tree | 6661d4e20f6d4bf79f82800c3686613c4fbb16de /README.commits | |
| parent | 0dd7155f79407630755764b91bf1baaf7cdf5806 (diff) | |
| download | gtk+-5ef4c2b9bdf6df0711b62502c2cff68be2daef54.tar.gz | |
Update README files to refer to git
Update various README files to refer to git instead of svn.
Also discontinue ChangeLog files.
Diffstat (limited to 'README.commits')
| -rw-r--r-- | README.commits | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/README.commits b/README.commits index 392b7acdf4..f6e830a2ce 100644 --- a/README.commits +++ b/README.commits @@ -4,8 +4,8 @@ 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 last 4 years, we'd like -to ask people committing to GTK+ to follow a few rules: +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 |