| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | SNIA | 57 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | CUA-OPL-1.0 | 165 months after the date it initially became available, or at least six
166 (6) months after a subsequent version of that particular Modification
|
| H A D | MPL-1.1 | 64 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | SugarCRM-1 | 146 at least twelve (12) months after the date it initially became available, or at
147 least six (6) months after a subsequent version of that particular Modification
|
| H A D | SugarCRM-1.1.3 | 65 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | Interbase-1.0 | 74 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | BitTorrent-1.0 | 122 months after the date it initially became available, or at least six (6) months after a subsequent …
|
| H A D | NOSL | 57 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | CPAL-1.0 | 38 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | NPL-1.1 | 100 …n available for at least twelve (12) months after the date it initially became available, or at le…
|
| H A D | APSL-2.0 | 43 …ow, for as long as you Externally Deploy the Covered Code or twelve (12) months from the date of i…
|
| H A D | APSL-1.2 | 40 …ction 3 below, for as long as you Deploy the Covered Code or twelve (12) months from the date of i…
|
| H A D | APSL-1.0 | 113 Covered Code or twelve (12) months from the date of initial
|
| H A D | APSL-1.1 | 118 Covered Code or twelve (12) months from the date of initial
|
| /openbmc/linux/Documentation/block/ |
| H A D | data-integrity.rst | 10 corruption is done at read time which could potentially be months
|
| /openbmc/linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 99 requiring months or years of effort before the code can be brought up to
|
| H A D | handling-regressions.rst | 127 into the issue weeks, months, or years later. These tags are also crucial for
196 twelve months before the current development cycle ends: Linus wants such
223 twelve months, ensure to tag the fix with "Cc: stable@vger.kernel.org", as a
|
| H A D | submitting-patches.rst | 656 when, two or three months later, they are going through perhaps
703 weeks, months or even years later, it can give the reader the needed
|
| /openbmc/linux/LICENSES/dual/ |
| H A D | MPL-1.1 | 178 months after the date it initially became available, or at least six
179 (6) months after a subsequent version of that particular Modification
|
| /openbmc/linux/arch/arm/tools/ |
| H A D | mach-types | 17 # within the last 12 months. References to machine_is_NAME() do not count!
|
| /openbmc/webui-vue/docs/guide/components/table/ |
| H A D | index.md | 54 age: '4 months',
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/ |
| H A D | ui-bootstrap-tpls-0.11.0.js | 8 …months||0);i.activeDate.setFullYear(b,c,1),i.refreshView()},a.toggleMode=function(b){b=b||1,a.date… property in e.step
|
| H A D | ui-bootstrap-tpls-0.11.0.min.js | 8 …months||0);i.activeDate.setFullYear(b,c,1),i.refreshView()},a.toggleMode=function(b){b=b||1,a.date… property in e.step
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | signature.txt | 464 <n>m = key expires in n months
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-self-describing-metadata.rst | 33 to analyse and so that analysis blows out towards weeks/months of forensic work.
|