Search results

  • ...developers/ Arch Linux developers] either by mail or IRC to see your patch committed in your name.
    758 bytes (114 words) - 09:10, 5 July 2021
  • ...the package (a package could have been worked on by three people and then committed by one of them). All developers are equally "to blame" for any "mistakes" i
    2 KB (359 words) - 13:01, 11 December 2020
  • * sshd role stuff has been figured out and will soon be committed in Git
    2 KB (221 words) - 09:27, 5 July 2020
  • ...of providing data to APNIC labs for research purposes. APNIC and Cloudfare committed to treat all data with high privacy standards in their [https://labs.apnic.
    6 KB (756 words) - 13:51, 30 November 2020
  • ...ocally, and any subsequent changes made to the files will be automatically committed to the remote.
    2 KB (394 words) - 10:21, 26 September 2021
  • ...because the data is written to disk twice: once to the journal then later committed to the main filesystem, but this does not seem to be the case. I have enabl
    8 KB (1,395 words) - 07:19, 20 January 2022
  • This looks very promising and ReubenBond is committed to developing a driver in the next few weeks. This is all referenced in the
    6 KB (926 words) - 12:27, 8 May 2021
  • ...orded (committed) to the repository. Git also lets you restore, previously committed, working tree files. * Show changes to be committed, unstaged changes and untracked files
    27 KB (4,007 words) - 11:38, 5 September 2021
  • ...orded (committed) to the repository. Git also lets you restore, previously committed, working tree files. * Show changes to be committed, unstaged changes and untracked files
    26 KB (3,766 words) - 05:51, 7 July 2021
  • ...a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; when shared configuration is modified in th
    18 KB (2,294 words) - 16:29, 5 December 2021
  • ...commit firmware to specified slot. In the example below, firmware is first committed without activation ({{ic|-a 0}}). Next, an existing image is activated ({{i
    13 KB (1,876 words) - 18:46, 24 November 2021
  • ...]. Journaling provides fault-resilience by logging changes before they are committed to the file system. In the event of a system crash or power failure, such f
    20 KB (2,885 words) - 19:03, 25 January 2022
  • ## If there packages to add, then each package is committed
    40 KB (6,217 words) - 07:08, 24 January 2022
  • .... Btrfs defaults to a 30 seconds checkpoint interval in which new data are committed to the filesystem. This can be changed by appending the {{ic|commit}} mount
    43 KB (6,692 words) - 19:54, 21 January 2022
  • .... Btrfs defaults to a 30 seconds checkpoint interval in which new data are committed to the filesystem. This can be changed by appending the {{ic|commit}} mount
    46 KB (7,224 words) - 18:35, 6 January 2022
  • ...can tell ZFS to prefer to not use the ZIL, and in which case, data is only committed to the file system once. Setting this for non-database file systems, or for
    42 KB (6,197 words) - 22:14, 21 January 2022
  • ...cks are a potential privacy leak, Arch Linux's default connectivity URL is committed to not logging any access. See [https://gitlab.archlinux.org/archlinux/infr
    68 KB (10,012 words) - 15:28, 9 January 2022
  • ...can tell ZFS to prefer to not use the ZIL, and in which case, data is only committed to the file system once. However, doing so on non-solid state storage (e.g.
    73 KB (11,420 words) - 18:08, 17 January 2022