aboutsummaryrefslogtreecommitdiffstats
path: root/libical/design-data/status.txt
diff options
context:
space:
mode:
authorSeth Alves <alves@src.gnome.org>2000-02-21 21:19:28 +0800
committerSeth Alves <alves@src.gnome.org>2000-02-21 21:19:28 +0800
commitc2e1263462c84bfae59a3f296758296ac3a10a67 (patch)
tree56965c52067222cac0199e2a09d33ef93b0dcb4d /libical/design-data/status.txt
parentc69d6adfcd4b6ef04cae78c87f2328b8debb13bb (diff)
downloadgsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.tar
gsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.tar.gz
gsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.tar.bz2
gsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.tar.lz
gsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.tar.xz
gsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.tar.zst
gsoc2013-evolution-c2e1263462c84bfae59a3f296758296ac3a10a67.zip
This commit was generated by cvs2svn to compensate for changes in r1879,
which included commits to RCS files with non-trunk default branches. svn path=/trunk/; revision=1880
Diffstat (limited to 'libical/design-data/status.txt')
-rw-r--r--libical/design-data/status.txt36
1 files changed, 18 insertions, 18 deletions
diff --git a/libical/design-data/status.txt b/libical/design-data/status.txt
index c3a4c2580d..d3f2f1864d 100644
--- a/libical/design-data/status.txt
+++ b/libical/design-data/status.txt
@@ -1,32 +1,32 @@
2.0 Success.
-2.1 Success but fallback taken on one or more property values.
-2.2 Success, invalid property ignored.
-2.3 Success, invalid property parameter ignored.
-2.4 Success, unknown non- standard property ignored.
-2.5 Success, unknown non standard property value ignored.
-2.6 Success, invalid calendar component ignored.
-2.7 Success, request forwarded to Calendar User.
-2.8 Success, repeating event ignored. Scheduled as a single component.
-2.9 Success, truncated end date time to date boundary.
-2.10 Success, repeating VTODO ignored. Scheduled as a single VTODO.
-2.11 Success, unbounded RRULE clipped at some finite number of instances
+2.1 Success but fallback taken on one or more property values.
+2.2 Success, invalid property ignored.
+2.3 Success, invalid property parameter ignored.
+2.4 Success, unknown non-standard property ignored.
+2.5 Success, unknown non-standard property value ignored.
+2.6 Success, invalid calendar component ignored.
+2.7 Success, request forwarded to Calendar User.
+2.8 Success, repeating event ignored. Scheduled as a single component.
+2.9 Success, truncated end date time to date boundary.
+2.10 Success, repeating VTODO ignored. Scheduled as a single VTODO.
+2.11 Success, unbounded RRULE clipped at some finite number of instances
3.0 Invalid property name.
3.1 Invalid property value.
3.2 Invalid property parameter.
-3.3 Invalid property parameter value.
-3.4 Invalid calendar component sequence.
+3.3 Invalid property parameter value.
+3.4 Invalid calendar component sequence.
3.5 Invalid date or time.
3.6 Invalid rule.
3.7 Invalid Calendar User.
3.8 No authority.
3.9 Unsupported version.
3.10 Request entity too large.
-3.11 Required component or property missing.
-3.12 Unknown component or property found
-3.13 Unsupported component or property found
+3.11 Required component or property missing.
+3.12 Unknown component or property found
+3.13 Unsupported component or property found
3.14 Unsupported capability
-4.0 Event conflict. Date/time is busy.
+4.0 Event conflict. Date/time is busy.
5.0 Request MAY supported.
5.1 Service unavailable.
5.2 Invalid calendar service.
-5.3 No scheduling support for user.
+5.3 No scheduling support for user.