Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | README.Debian: Fix typo | Reinhard Tartler | 2018-02-20 |
| | |||
* | Clarify how the upstream tarball is produced | Reinhard Tartler | 2017-06-17 |
| | | | | | The "upstream" tarball is produced using git-archive from the upstream git branch at github: | ||
* | README.Debian: Fix some typos | Reinhard Tartler | 2017-06-16 |
| | | | | Found by lintian | ||
* | update urls in debian specific documentation to boxbackup.org | Reinhard Tartler | 2009-04-01 |
| | |||
* | add some notes about the upstream tarball situation | Reinhard Tartler | 2009-04-01 |
| | |||
* | add packaging | Reinhard Tartler | 2008-07-24 |
| | |||
* | Import of boxbackup 0.10 | Reinhard Tartler | 2008-01-19 |
| | | | | | | | | | | | This is actually a quite funny commit: I had started my packaging branch in a strange way: I did not start from a clean tarball, but used an existing packaging directory as starting place. This makes upgrading to a new upstream hard. So I branched revision 1, and 'bzr import'ed the Upstream tarball of version 0.10 over it. The upstream tarball version I used for this commit has the md5sum: 2dc02d87932fdb222ed019443ddcf444 | ||
* | initial commit | Reinhard Tartler | 2007-02-14 |