From Fedora Project Wiki

  • ...d in the stable two week push, we would then tag that commit with a stable ref at compose push live time the ref would be something like '''fedora-atomic/24/x86_64/stable-docker-host''' an
    1 KB (178 words) - 13:49, 7 October 2016
  • ref: master ref: master
    6 KB (821 words) - 12:55, 28 November 2018
  • ...r message when creating a user account, where account name already exists</ref> ...CD removed pam_cracklib.so from system-auth. Once re-added, the test PASS</ref>
    9 KB (1,386 words) - 19:38, 26 June 2015
  • ref: branch-tag-or-commit-hash ref: master
    21 KB (2,809 words) - 08:19, 15 October 2018
  • ...his basically points out that every pull request should be given an unique ref/ID using which it can be fetched locally , doing that will create a new bra
    10 KB (1,676 words) - 05:51, 27 April 2016
  • ref: master
    6 KB (828 words) - 17:01, 14 December 2017
  • ...self-documented about the implications of these LABELs (or at least a link/ref to Fedora Container Guidelines) Typically, a RPM has a very specific git ref that correlates to a N-V-R, this is not the case in container land.
    13 KB (1,845 words) - 18:39, 13 March 2017
  • [Flatpak Ref]
    6 KB (925 words) - 21:53, 6 June 2018
  • ...d 'master' from being pushed at all. Additionally, we will establish a sym-ref between 'rawhide' and 'main' as a convenience for people who prefer to use
    8 KB (1,088 words) - 08:40, 8 February 2021
  • ...uests. It will furthermore specify that the module wants a particular git ref of those components. The validation step here includes checking out those
    6 KB (1,101 words) - 14:26, 11 April 2017
  • ref: private-rawhide-autoconf-2.71 ref: private-rawhide-autoconf-2.71
    18 KB (2,857 words) - 13:11, 26 August 2021
  • ...g those in one text file and telling people to use. A licensed REF license ref is an spdx. Specification. Designation for a licenses, It's not on. ...hat added to the collected file and not need to come up with a new license ref for each one that seems very sensible. It's
    46 KB (8,372 words) - 16:35, 12 April 2023
  • | OmniVision "2800" ref. board || 05a9:2800 || ovfx2 || OV3610 || good (5)
    7 KB (1,065 words) - 21:41, 17 September 2016
  • ...User:Dcantrell|David Cantrell]], [[User:Jlovejoy|Jilayne Lovejoy]], [[User:Ref|Richard Fontana]] || Fedora adopts SPDX licensing expressions. How the pro
    9 KB (1,262 words) - 18:04, 8 September 2023
  • ...s or co-writers) budget planning process''' in APAC in the last two years. Ref: [[Ambassadors/APAC/Budget#References]]
    8 KB (1,089 words) - 05:53, 19 July 2016
  • ...s or co-writers) budget planning process''' in APAC in the last two years. Ref: [[Ambassadors/APAC/Budget#References]]
    10 KB (1,347 words) - 10:58, 24 March 2019
  • | OmniVision "2800" ref. board || 05a9:2800 || ovfx2 || ov3610 || good (5)
    9 KB (1,368 words) - 21:41, 17 September 2016
  • ...uthority,OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),O=Entrust.net,C=US ...uthority,OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),O=Entrust.net,C=US
    25 KB (3,821 words) - 18:49, 26 April 2017
  • ...s or co-writers) budget planning process''' in APAC in the last two years. Ref: [[Ambassadors/APAC/Budget#References]]
    14 KB (1,803 words) - 11:00, 24 March 2019
  • ...014 ([http://en.wikipedia.org/wiki/University_of_Colorado_Colorado_Springs ref]) UCCS is a well-ranked school with a beautiful campus.
    12 KB (1,963 words) - 15:59, 23 March 2019
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)