/openbmc/openbmc/.github/ |
H A D | stale.yml | 3 # Number of days of inactivity before an issue becomes stale (6 months) 15 occurred in the last 6 months. It will be closed if no activity occurs in the 22 months. Please reopen if this issue should not have been closed. Thank you
|
/openbmc/u-boot/drivers/rtc/ |
H A D | mcfrtc.c | 59 int days, i, months; in rtc_set() local 77 months = tmp->tm_mon - 1; in rtc_set() 78 for (i = 0; i < months; i++) { in rtc_set()
|
/openbmc/docs/tof/ |
H A D | membership-and-voting.md | 30 months in which half (+/- 1) of the seats are re-elected. Due to additions or 72 Membership is determined using data from the previous 6 months of development 75 6 months, but does not qualify in the most recent 6 months, will be listed as an 76 Member Emeritus for 6 months. Both Active and Emertius members are eligible for 123 Points required for Active membership (in the preceding 6 months):
|
/openbmc/bmcweb/redfish-core/include/utils/extern/ |
H A D | date.h | 200 using months = std::chrono::duration variable 1563 month::operator+=(const months& m) NOEXCEPT 1572 month::operator-=(const months& m) NOEXCEPT 1631 months 1635 return months(d <= 11 ? d : d + 12); 1641 operator+(const month& x, const months& y) NOEXCEPT 1651 operator+(const months& x, const month& y) NOEXCEPT 1659 operator-(const month& x, const months& y) NOEXCEPT 2205 year_month::operator+=(const months& dm) NOEXCEPT 2215 year_month::operator-=(const months& dm) NOEXCEPT [all …]
|
/openbmc/u-boot/board/compulab/common/ |
H A D | eeprom.c | 260 char *months[12] = {"Jan", "Feb", "Mar", "Apr", "May", "Jun", variable 278 printf("%s", months[field->buf[1] - 1]); in eeprom_field_print_date() 364 if (!strcmp(tok2, months[month - 1])) in eeprom_field_update_date()
|
/openbmc/linux/Documentation/arch/openrisc/ |
H A D | todo.rst | 7 the coming months. Here's a list of known-to-be-less-than-stellar items
|
/openbmc/docs/ |
H A D | community-membership.md | 70 - Member for at least 3 months 108 - Member for at least 3 months 152 - Reviewer of the codebase for at least 9 months
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | LPPL-1.3c | 246 of communication for a period of six months, and there are no other 280 and after three months your intention is challenged neither by 286 reachable once more within three months of a change completed
|
H A D | LPPL-1.3a | 95 …reached through the indicated means of communication for a period of six months, and there are no … 113 …4. If you make an `intention announcement' as described in 2b. above and after three months your i… 115 … unreachable Current Maintainer becomes reachable once more within three months of a change comple…
|
H A D | ErlPL-1.1 | 124 remain available for at least twelve (12) months after the date it 125 initially became available, or at least six (6) months after a
|
H A D | MPL-1.0 | 52 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
H A D | FreeImage | 55 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
H A D | APL-1.0 | 105 …n Electronic Distribution Mechanism for a period of at least twelve (12) months. The aforesaid twe… 115 …months, to give any third party under the terms of this License, for a charge no more than the cos…
|
H A D | Motosoto | 187 least twelve (12) months after the date it initially became 188 available, or at least six (6) months after a subsequent version
|
H A D | Nokia | 170 must remain available for at least twelve (12) months after the date it 171 initially became available, or at least six (6) months after a subsequent
|
H A D | RSCPL | 84 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
H A D | OPL-1.0 | 54 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
H A D | NPL-1.0 | 35 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
H A D | SPL-1.0 | 175 months after the date it initially became available, or at least six 176 (6) months after a subsequent version of that particular Modification
|
H A D | RHeCos-1.1 | 58 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
H A D | RHeCos-1 | 121 (12) months after the date it initially became available, or at least six (6) 122 months after a subsequent version of that particular Modification has been made
|
/openbmc/linux/fs/reiserfs/ |
H A D | README | 131 Chris Mason dived right into our code, and in just a few months produced
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | release-process.rst | 95 While stable releases are supported for a duration of seven months,
|
/openbmc/linux/Documentation/trace/ |
H A D | tracepoint-analysis.rst | 338 forgotten about from months ago!
|
/openbmc/linux/Documentation/process/ |
H A D | 7.AdvancedTopics.rst | 74 you have been working on it for months. Changes can be transparently
|