Skip to content


Subversion checkout URL

You can clone with
Download ZIP

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
base fork: gutenye/gutbackup
base: d4ce2bd3a2
head fork: gutenye/gutbackup
compare: 0cf58031c2
  • 1 commit
  • 2 files changed
  • 0 commit comments
  • 1 contributor
Commits on Sep 18, 2012
@gutenye add 0cf5803
Showing with 25 additions and 12 deletions.
  1. +17 −0
  2. +8 −12
@@ -0,0 +1,17 @@
+We love pull requests. Here's a quick guide:
+1. Fork the repo.
+2. Create a topic branch from where you want to base your work.
+3. Add a test for your change. Only refactoring and documentation changes
+require no new tests. If you are adding functionality or fixing a bug, we need
+a test!
+4. Make the test pass with `rake test`.
+5. Push to your fork and submit a pull request.
+6. Coding Style Guide:
+And in case we didn't emphasize it enough: we love tests!
@@ -124,27 +124,23 @@ Install
# Archlinux
- pacman -S ruby rsync
gem install oldtime
+ pacman -S ruby rsync
# /etc/cron.weekly/cleanup_pkg
pacman -Sc --noconfirm
+Development [![Dependency Status](]( [![Code Climate](](
-Note on Patches/Pull Requests
-1. Fork the project.
-2. Make your feature addition or bug fix.
-3. Add tests for it. This is important so I don't break it in a future version unintentionally.
-4. Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
-5. Send me a pull request. Bonus points for topic branches.
-6. Coding Style Guide:
+* Submit any bugs/features/ideas to github issue tracker.
+Please see [Contibution Documentation](
-* [Contributors](
+A list of [Contributors](

No commit comments for this range

Something went wrong with that request. Please try again.