| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix trailing-whitespace for entire project | Allen Winter | 2022-09-24 | 1 | -5/+5 |
| | | |||||
| * | Internally represent GEO properties as text | Allen Winter | 2022-06-11 | 1 | -1/+1 |
| | | | | | | | This allows arbitrary precision for the GEO values fixes: #531 | ||||
| * | REUSE compliance | Allen Winter | 2022-06-06 | 1 | -1/+2 |
| | | | | | fixes: #489 | ||||
| * | design-data/parameters.csv: Fix enum value clashing | Allen Winter | 2022-04-28 | 1 | -3/+2 |
| | | | | | | | | | | | | | | | From: Milan Crha <mcrha@redhat.com> Date: Wed, 27 Apr 2022 12:37:46 +0200 Subject: [PATCH] parameters.csv: Fix enum value clashing Two problems: * EMAIL being defined twice * REASON and REQUIRED use the same value The effect of this patch is that only the ICAL_REASON_PARAMETER value changes from 43 to 47, the ICAL_EMAIL_PARAMETER value stays unchanged. | ||||
| * | design-data/value-types.csv - fix enum ICAL_ICAL_PROXIMITY_VALUE | Allen Winter | 2022-04-28 | 1 | -1/+1 |
| | | | | | | | | ICAL_DATETIMEDATE_VALUE and ICAL_PROXIMITY_VALUE were set to the same value (5036). Now ICAL_DATETIMEDATE_VALUE=5036 and ICAL_PROXIMITY_VALUE=5039 | ||||
| * | design-data/properties.csv - remove dupe entry for "NAME" | Allen Winter | 2022-04-28 | 1 | -3/+3 |
| | | | | | | | | | | | | | | | There were 2 NAME properties: * CAP Properties","RFC 4324 Section 2.1.2", NAME - used to add locale-specific descs to components. * Properties for iCalendar","RFC 7986 Section 5", NAME - specifies the name of the calendar. Now we have 1 property that can have either context but uses the same enum value (151). RFCs shouldn't use the same identifier string to describe two different contexts. | ||||
| * | LOCATION-TYPE is a multivalued property | Ken Murchison | 2022-01-18 | 1 | -1/+1 |
| | | |||||
| * | restrictions.csv, icalrestriction.c.in: consolidate VALARM restrictions and ↵ | Ken Murchison | 2022-01-18 | 1 | -195/+57 |
| | | | | | validation functions | ||||
| * | icalrestriction.c.in: consolidate STATUS value validation functions | Ken Murchison | 2022-01-18 | 1 | -12/+12 |
| | | |||||
| * | Add Event Publishing Extensions (RFC 9073) components, properties, ↵ | Ken Murchison | 2022-01-18 | 6 | -3/+309 |
| | | | | | parameters, values | ||||
| * | value-types.csv: add blank lines for readability | Ken Murchison | 2022-01-18 | 1 | -0/+9 |
| | | |||||
| * | properties.csv: add blank lines for readability | Ken Murchison | 2022-01-18 | 1 | -0/+13 |
| | | |||||
| * | parameters.csv: add comment for RELTYPE:SNOOZE | Ken Murchison | 2022-01-18 | 1 | -0/+1 |
| | | |||||
| * | parameters.csv: add blank lines for readability | Ken Murchison | 2022-01-18 | 1 | -0/+9 |
| | | |||||
| * | value-types.csv: fix comment | Ken Murchison | 2022-01-18 | 1 | -1/+1 |
| | | |||||
| * | Add/update: VALARM Extensions (RFC 9074) properties, parameters, values | Ken Murchison | 2022-01-18 | 4 | -2/+6 |
| | | |||||
| * | restrictions.csv: fix typo | Ken Murchison | 2022-01-06 | 1 | -1/+1 |
| | | |||||
| * | restrictions.csv: DECLINECOUNTER,VEVENT: DURATION and DTEND are mutually ↵ | Дилян Палаузов | 2021-11-08 | 1 | -3/+3 |
| | | | | | | | | | | exclusive My reading of https://datatracker.ietf.org/doc/html/rfc5546#section-3.2.8 is that for METHOD:DECLINECOUNTER either DTEND or DURATION must be present. If both are absent, the usual logic of calculating the end applies, based on the value-type of DTSTART. | ||||
| * | Fix typos and misspellings found by CodeSpell 2.1.0. | Shaun Case | 2021-07-12 | 2 | -2/+2 |
| | | | | | Fix a few Python whitespace errors found by Syntastic. | ||||
| * | restrictions: VTIMEZONE can contain any number of X properties | Дилян Палаузов | 2020-10-24 | 1 | -1/+1 |
| | | |||||
| * | design-data/properties.csv - allow COMPLETED property to be a date or datetime | Allen Winter | 2018-02-19 | 1 | -1/+1 |
| | | |||||
| * | value-types.csv: Added STATUS:DELETEDvpatch | Ken Murchison | 2017-10-21 | 1 | -1/+1 |
| | | |||||
| * | Initial VPATCH implementation | Ken Murchison | 2017-02-14 | 5 | -1/+30 |
| | | |||||
| * | - handle properties which don't have "default" value types | Ken Murchison | 2016-12-23 | 1 | -15/+15 |
| | | | | | | - better handling of multi-valued properties and valid value type checking - suppress VALUE= parameter on properties when they contain the default value type | ||||
| * | created new DATE-TIME-DATE type for those properties that accept both ↵ | Ken Murchison | 2016-12-20 | 2 | -7/+8 |
| | | | | | | | DATE-TIME and DATE. DATE and DATE-TIME now only accept the proper values (date without time and date with time respectively) | ||||
| * | icalderivedvalue.c.in: icalvalue_new/set/get_binary() need to use v_attach ↵ | Ken Murchison | 2016-12-18 | 1 | -1/+1 |
| | | | | | data element to match what icalparser.c does with ATTACH;VALUE=BINARY | ||||
| * | parameters.csv: Managed Attachments is now a CALEXT WG document | Ken Murchison | 2016-11-12 | 1 | -1/+1 |
| | | |||||
| * | draft-ietf-calext-extensions is now RFC 7986 | Ken Murchison | 2016-10-19 | 2 | -2/+2 |
| | | |||||
| * | update restrictions on properties modified by ↵ | Ken Murchison | 2016-09-03 | 1 | -5/+5 |
| | | | | | draft-ietf-calext-extensions-05 (soon to be RFC) | ||||
| * | VAVAILABILITY spec is now RFC 7953 | Ken Murchison | 2016-08-30 | 2 | -2/+2 |
| | | |||||
| * | added properties and parameters from draft-ietf-calext-extensions | Ken Murchison | 2016-06-26 | 4 | -6/+92 |
| | | |||||
| * | properties.csv: note that EXRULE has been deprecated | Ken Murchison | 2015-08-18 | 1 | -2/+3 |
| | | |||||
| * | properties.csv: fix section numbers in RFC 5545 reference | Ken Murchison | 2015-08-18 | 1 | -1/+1 |
| | | |||||
| * | parameters.csv: fix title of RFC 6638 | Ken Murchison | 2015-08-18 | 1 | -1/+1 |
| | | |||||
| * | Added new Task Extensions properties, parameters, and parameter values ↵ | Ken Murchison | 2015-03-05 | 4 | -9/+19 |
| | | | | | (draft-apthorp-ical-tasks) | ||||
| * | Fix missing or stray double quotes in design-data. | Robert Stepanek | 2015-03-03 | 2 | -5/+5 |
| | | |||||
| * | design-data/parameters.csv,value-types.csv: spread out parameter/value-type ↵ | Ken Murchison | 2015-02-19 | 2 | -31/+35 |
| | | | | | enum values so that future values can be inserted in the X -> NONE range without breaking binary compatibility and functions like icalproperty_xxx_to_string() continue to operate correctly | ||||
| * | Merge branch 'master' of github.com:libical/libical | Ken Murchison | 2015-01-20 | 3 | -6/+0 |
| |\ | |||||
| | * | Merge branch 'coverity_scan' | Allen Winter | 2014-12-06 | 1 | -6/+0 |
| | |\ | |||||
| | | * | remove .svnignore files | Allen Winter | 2014-11-28 | 1 | -6/+0 |
| | | | | |||||
| | * | | remove execute permissions | Allen Winter | 2014-12-06 | 2 | -0/+0 |
| | |/ | |||||
| * | | Updated VPOLL to draft-york-vpoll-03 (restrictions are still a work in progress) | Ken Murchison | 2015-01-20 | 6 | -18/+74 |
| |/ | |||||
| * | Saving files before refreshing line endings | Allen Winter | 2014-11-23 | 2 | -0/+0 |
| | | |||||
| * | issue177: CalDAV attachments as in draft-daboo-caldav-attachments | Allen Winter | 2014-11-11 | 2 | -1/+5 |
| | | |||||
| * | design-data: renamed EQUIVALENT-TZID to TZID-ALIAS-OFv1.0.1 | Ken Murchison | 2014-10-09 | 2 | -2/+2 |
| | | |||||
| * | value-types.csv: make sure icalvalue_kind enum values match those in libical-1.0 | Ken Murchison | 2014-09-29 | 1 | -29/+29 |
| | | |||||
| * | Add properties from draft-ietf-tzdist-service | Ken Murchison | 2014-09-16 | 2 | -0/+5 |
| | | |||||
| * | Re-arrange after svn to git conversion | Allen Winter | 2014-05-31 | 9 | -0/+2161 |
 |
index : delta/libical-git.git | |
| github.com: libical/libical.git |
| summaryrefslogtreecommitdiff |
path: root/design-data