]> err.no Git - dak/commit
projects / dak / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8f1fd2c) | patch
rename volatile to updates
authorJoerg Jaspert <joerg@debian.org>
Sun, 28 Nov 2010 22:36:38 +0000 (23:36 +0100)
committerJoerg Jaspert <joerg@debian.org>
Sun, 28 Nov 2010 22:36:38 +0000 (23:36 +0100)
commit1fc854e1829ed9000f02ea1375201366625d73c8
tree497d3063a72f79ba226717516e36ce83ee2cb88ctree | snapshot
parent8f1fd2cd970d092854d7bf828d02daa1b849383ecommit | diff
rename volatile to updates

what an insanity. We end up with things like Squeeze-Updates-Proposed-Updates.
Why the heck one cant just make p-u a full suite and recommend people to use that
too? Its after a "NEW" queue anyways. This only serves to needlessly confuse
users. "What? proposed-updates and updates? whats going on?"
Meh. Volatile might be a bad name, but now this is worse.

Signed-off-by: Joerg Jaspert <joerg@debian.org>
config/debian/apache.conf-incoming diff | blob | history
config/debian/apt.conf diff | blob | history
config/debian/dak.conf diff | blob | history
dak/dakdb/update40.py [new file with mode: 0755] blob
dak/generate_packages_sources.py diff | blob | history
daklib/queue.py diff | blob | history
scripts/debian/import_dataset.sh diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.