docs-commits October 2014

docs-commits@lists.fedoraproject.org

9 participants
171 discussions

[release-notes] remove prerelease content in preparation for F21
by Pete Travis 04 Oct '14

04 Oct '14

commit 08ac9838c45288369af3faa59b98a620c5926dd2 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Oct 4 12:21:23 2014 -0600 remove prerelease content in preparation for F21 en-US/Release_Notes.xml | 3 - en-US/prerelease.xml | 141 ----------------------------------------------- 2 files changed, 0 insertions(+), 144 deletions(-) --- diff --git a/en-US/Release_Notes.xml b/en-US/Release_Notes.xml index 37a533d..2de8f27 100644 --- a/en-US/Release_Notes.xml +++ b/en-US/Release_Notes.xml @@ -13,9 +13,6 @@ <xi:include href="Section-Welcome.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="prerelease.xml" - xmlns:xi="http://www.w3.org/2001/XInclude" /> -

1 0

[release-notes/prerelease: 9/9] Merge branch 'master' into prerelease
by Pete Travis 04 Oct '14

04 Oct '14

commit 8b405b55c31054c85ba3d8d8303d421d980a7163 Merge: 7b53c09 6e8cfc3 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sat Oct 4 12:13:32 2014 -0600 Merge branch 'master' into prerelease This should be where the content for rawhide/branched RNs lives. build/fedora-release-notes.desktop | 7 +++++-- en-US/Article_Info.xml | 2 +- 2 files changed, 6 insertions(+), 3 deletions(-) ---

1 0

[release-notes/prerelease] (9 commits) ...Merge branch 'master' into prerelease
by Pete Travis 04 Oct '14

04 Oct '14

Summary of changes: 4751f62... markup fix (*) 03e9560... change seed .desktop file to launch ephiphany webapp (*) d8e8ca7... removing stale release name reference from article info (*) fba02ce... updating launch path in desktop file (*) 5ab4188... Rookie mistakes: mkdir doesn't do parents unless you tell i (*) fad4653... if you have the repo on more than one machine, commits are (*) bfbd1a2... fix webapp.desktop path, and fall back to default html hand (*) 6e8cfc3... desktop-file-validate is a good tool, use it (*) 8b405b5... Merge branch 'master' into prerelease (*) This commit already existed in another branch; no separate mail sent

1 0

[securityguide] add recommandation
by Fabian Affolter 04 Oct '14

04 Oct '14

commit a7b06bdc34a327d4fd01308cabc2ff4a2b0828c2 Author: Fabian Affolter <fab(a)fedoraproject.org> Date: Sat Oct 4 10:07:34 2014 +0200 add recommandation en-US/Yubikey.xml | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-) --- diff --git a/en-US/Yubikey.xml b/en-US/Yubikey.xml index 6f6d9de..3262a56 100644 --- a/en-US/Yubikey.xml +++ b/en-US/Yubikey.xml @@ -18,7 +18,10 @@ <procedure> <step> <para> - Install <package>pam_yubico</package> + Install <package>pam_yubico</package> as root. + </para> + <para> + <command>yum install pam_yubico</command> </para> </step> <step> @@ -26,7 +29,7 @@ For two factor authentication open <filename>/etc/pam.d/gdm-password</filename> and locate the following line: </para> <para> - <command>auth substack password-auth </command> + <command>auth substack password-auth </command> </para> <para> In a new line after this add: @@ -37,7 +40,7 @@ </step> <step> <para> - To simple use the yubikey token without your password remove the first line from the step above and replace it with the second. + To simple use the yubikey token without your password remove the first line from the step above and replace it with the second. It's not recommanded to use the yubikey without a password. </para> </step> <step>

1 0

[firewall-guide] master: Update subtitle and abstract (47e26ff)
by Pete Travis 02 Oct '14

02 Oct '14

Repository : http://git.fedorahosted.org/cgit/docs/firewall-guide.git On branch : master >--------------------------------------------------------------- commit 47e26ffac9d6fa1d5d5a5c87d57c3ad3cc6ca672 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Thu Oct 2 13:02:06 2014 -0600 Update subtitle and abstract >--------------------------------------------------------------- en-US/Book_Info.xml | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml index 79a0eb1..ab8e627 100644 --- a/en-US/Book_Info.xml +++ b/en-US/Book_Info.xml @@ -5,14 +5,14 @@ ]> <bookinfo id="book-Documentation-firewall-guide-firewall_guide"> <title>firewall-guide</title> - <subtitle>Enter a short description here.</subtitle> + <subtitle>Firewall function and administration on Fedora</subtitle> <productname>Documentation</productname> - <productnumber>01</productnumber> + <productnumber>21</productnumber> <edition>21</edition> <pubsnumber>0</pubsnumber> <abstract> - <para> - A short overview and summary of the book's subject and purpose, traditionally no more than one paragraph long. Note: the abstract will appear in the front matter of your book and will also be placed in the description field of the book's RPM spec file. + <para> + A practical guide that explains how firewalls function, their role in network security, and how to administer them. The guide provides both general knowledge, and specific examples for common tasks. </para> </abstract> <corpauthor>

1 0

[install-guide/F21-rewrite] Expanding information on autostep in Kickstart Syntax Reference
by pbokoc 02 Oct '14

02 Oct '14

commit 1eb684506846b1a395674bd8538e8b5c2273a228 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Thu Oct 2 15:32:39 2014 +0200 Expanding information on autostep in Kickstart Syntax Reference en-US/Kickstart_Syntax_Reference.xml | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) --- diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index 2cd58bc..529031e 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -3047,7 +3047,10 @@ <term><option>--autoscreenshot</option></term> <listitem> <para> - Take a screenshot at every step during installation and copy the images over to <filename>/tmp/anaconda-screenshots</filename> after installation is complete. This is useful for documentation. + Take a screenshot at every step during installation. These screenshots are stored in <filename class="directory">/tmp/anaconda-screenshots</filename> during the installation, and after the installation finishes you can find them in <filename class="directory">/root/anaconda-screenshots</filename>. + </para> + <para> + Each screen is only captured right before the installer switches to the next one. This is important, because if you do not use all required Kickstart options and the installation therefore does not begin automatically, you can go to the screens which were not automatically configured, perform any configuration you want. Then, when you press <guilabel>Done</guilabel> to continue, the screen will be captured including the configuration you just provided. </para> </listitem> </varlistentry>

1 0

[install-guide/F21-rewrite] Typo fix
by pbokoc 02 Oct '14

02 Oct '14

commit 72b1c783abd3c71947972ece7feb4fae463fa3a2 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Wed Oct 1 17:07:38 2014 +0200 Typo fix en-US/Installing_Using_Anaconda.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml index 9e16ab7..8ec59f0 100644 --- a/en-US/Installing_Using_Anaconda.xml +++ b/en-US/Installing_Using_Anaconda.xml @@ -140,7 +140,7 @@ You can press <keycombo><keycap>Shift</keycap><keycap>Print Screen</keycap></keycombo> at any time during the graphical installation to capture the current screen. These screenshots are saved to <filename class="directory">/tmp/anaconda-screenshots</filename>. </para> <para> - Additionanlly, you can use the <command>autostep --autoscreenshot</command> command in a Kickstart file to capture and save each step of the installation automatically. See <xref linkend="sect-kickstart-commands-autostep" /> for details. + Additionally, you can use the <command>autostep --autoscreenshot</command> command in a Kickstart file to capture and save each step of the installation automatically. See <xref linkend="sect-kickstart-commands-autostep" /> for details. </para> </section>

1 0

[system-administrators-guide] Removing PackageKit chapter
by stephenw 01 Oct '14

01 Oct '14

commit a9de075a314a3ffc77c6db0d73db7821b754735f Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Wed Oct 1 21:33:37 2014 +0200 Removing PackageKit chapter echo 'GNOME' | sed 'ss.*s\L&s;ssoss;yymnynoy;ss.*s\u&!s' {it does not fit in the book anymore} en-US/PackageKit.xml | 631 --------------------------------- en-US/Preface.xml | 7 +- en-US/RPM.xml | 3 +- en-US/System_Administrators_Guide.xml | 3 +- en-US/Yum.xml | 3 +- 5 files changed, 5 insertions(+), 642 deletions(-) --- diff --git a/en-US/Preface.xml b/en-US/Preface.xml index a4fb09b..9456c66 100644 --- a/en-US/Preface.xml +++ b/en-US/Preface.xml @@ -12,7 +12,7 @@ <itemizedlist> <listitem> <para> - Installing and managing packages using the graphical <application>PackageKit</application> and command line <application>Yum</application> package managers + Installing and managing packages using <application>Yum</application> </para> </listitem> @@ -66,14 +66,11 @@ <term><xref linkend="part-Package_Management" /></term> <listitem> <para> - This part describes how to manage software packages on &MAJOROS; using both <application>Yum</application> and the <application>PackageKit</application> suite of graphical package management tools. + This part describes how to manage software packages on &MAJOROS; using <application>Yum</application>. </para> <para> <xref linkend="ch-yum" /> describes the <application>Yum</application> package manager. Read this chapter for information how to search, install, update, and uninstall packages on the command line. </para> - <para> - <xref linkend="ch-PackageKit" /> describes the <application>PackageKit</application> suite of graphical package management tools. Read this chapter for information how to search, install, update, and uninstall packages using a graphical user interface. - </para> </listitem> </varlistentry> <varlistentry> diff --git a/en-US/RPM.xml b/en-US/RPM.xml index 2984d61..482f897 100644 --- a/en-US/RPM.xml +++ b/en-US/RPM.xml @@ -23,8 +23,7 @@ <secondary>Yum instead of RPM</secondary> </indexterm>. <application>Yum</application> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <application>Yum</application> instead of RPM whenever possible to perform package management tasks. See <xref linkend="ch-yum"/>.</para> - <para>If you prefer a graphical interface, you can use the <application>PackageKit</application> GUI application, which uses <application>Yum</application> as its back end, to manage your system's packages. See <xref - linkend="ch-PackageKit"/> for details.</para> + <para>If you prefer a graphical interface, you can use the <application>PackageKit</application> GUI application, which uses <application>Yum</application> as its back end, to manage your system's packages.</para> </warning> <important> <title>Install RPM packages with the correct architecture!</title> diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml index cb5ae2a..5292977 100644 --- a/en-US/System_Administrators_Guide.xml +++ b/en-US/System_Administrators_Guide.xml @@ -24,11 +24,10 @@ <title>Package Management</title> <partintro> <para> - All software on a &MAJOROS; system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on &MAJOROS; using both <application>Yum</application> and the <application>PackageKit</application> suite of graphical package management tools. + All software on a &MAJOROS; system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on &MAJOROS; using <application>Yum</application>. </para> </partintro> <xi:include href="Yum.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PackageKit.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> <part id="part-Infrastructure_Services"> <title>Infrastructure Services</title> diff --git a/en-US/Yum.xml b/en-US/Yum.xml index c1f481a..4040576 100644 --- a/en-US/Yum.xml +++ b/en-US/Yum.xml @@ -16,8 +16,7 @@ Yum also enables you to easily set up your own repositories of <application>RPM</application> packages for download and installation on other machines. </para> <para> - Learning Yum is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <application>PackageKit</application> graphical package management tools. See <xref linkend="ch-PackageKit" /> for details on using <application>PackageKit</application>. - </para> + Learning Yum is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <application>PackageKit</application> graphical package management tools.</para> <note id="note-Note_Yum_and_Superuser_Privileges"> <title>Yum and superuser privileges</title> <para>

1 0

[multiboot-guide] master: bumping &PRODVER; to target F21 (13bb0c3)
by Pete Travis 01 Oct '14

01 Oct '14

1 0

[multiboot-guide] master: use the prompt tag (31b3324)
by Pete Travis 01 Oct '14

01 Oct '14

Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git On branch : master >--------------------------------------------------------------- commit 31b332438d736a33ff0f316b68b4fc79d84911fb Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Tue Sep 30 18:33:54 2014 -0600 use the prompt tag >--------------------------------------------------------------- en-US/Free_Space.xml | 33 +++++++++++++++++---------------- en-US/GRUB-configuration.xml | 6 +++--- en-US/GRUB-reinstalling.xml | 8 +++----- en-US/GRUB-runtime.xml | 4 ++-- en-US/Introduction.xml | 2 +- 5 files changed, 26 insertions(+), 27 deletions(-) diff --git a/en-US/Free_Space.xml b/en-US/Free_Space.xml index 5d93658..1e7535c 100644 --- a/en-US/Free_Space.xml +++ b/en-US/Free_Space.xml @@ -14,15 +14,16 @@ <para> The Fedora installer provides a guided graphical method for resizing partitions and reclaiming space. This method is simpler and easier than the others discussed in this section. For most simple dual boot situations, using the installer to reclaim space will be the most expedient and foolproof method. </para> + <remark>Check this link!</remark> <para> - Resizing partitions with the Fedora installer is covered in the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/recla…">Fedora Installation Guide</ulink> + Resizing partitions with the Fedora installer is covered in the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/recla…">Fedora Installation Guide</ulink> </para>  </section> - <section> + <section id="freespace-ntfs"> <title>Resizing an NTFS filesystem the command line</title> <para> This section explains using tools provided by Fedora to resize an NTFS partition. A terminal window from a liveCD can be used. @@ -36,7 +37,7 @@ http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-pa… <para> Show available filesystems: <screen> -# <command>blkid</command> + <prompt>#</prompt> <command>blkid</command> /dev/sda1: SEC_TYPE="msdos" UUID="32AE-E651" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="0315942d-8c2c-414f-a560-cfa499494a72" /dev/sda2: UUID="593153ae-2b67-4a5b-9efa-fa3954953abd" TYPE="ext4" PARTUUID="68cadad8-6de2-4ef7-96ff-f58e5114fdcc" /dev/sda3: UUID="P2xKTQ-aQWG-z2Uv-jSw5-kkUK-SN5Q-cNf3PI" TYPE="LVM2_member" PARTUUID="7ba7ed40-b43f-4e71-b83e-51629bf7db47" @@ -49,7 +50,7 @@ http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-pa… <para> <systemitem class="filesystem">ntfs</systemitem> partitions indicate the existing Windows installation. Examine the partitions on the <filename>/dev/sda</filename> drive. <screen> -# <command>parted /dev/sda print</command> + <prompt>#</prompt> <command>parted /dev/sda print</command> Model: ATA ST9320328CS (scsi) Disk /dev/sda: 320GB Sector size (logical/physical): 512B/512B @@ -70,7 +71,7 @@ Number Start End Size File system Name Flags <para> Partition number 5 is a large filesystem, and probably has some free space to share. Check how much of that space is in use. <screen> -# <command>ntfsresize --info /dev/sda5</command> + <prompt>#</prompt> <command>ntfsresize --info /dev/sda5</command> ntfsresize v2013.1.13 (libntfs-3g) Device name : /dev/sda5 NTFS volume version: 3.1 @@ -91,7 +92,7 @@ Please make a test run using both the -n and -s options before real resizing! <para> Resize the filesystem. Make sure to balance the available space, despite the suggestion from <application>ntfsresize</application> to shrink to the bare minimum. A very full filesystem can cause problems for any operating system. <screen> -# <command>ntfsresize --size 40G /dev/sda5</command> + <prompt>#</prompt> <command>ntfsresize --size 40G /dev/sda5</command> ntfsresize v2013.1.13 (libntfs-3g) Device name : /dev/sda5 NTFS volume version: 3.1 @@ -136,7 +137,7 @@ can recover the partition table by TestDisk or Parted's rescue mode. <para> To make sure that the partition is recreated accurately, work using sectors as units instead of bytes. The first figure we need is the sector the filesystem starts on. <screen> -# <command>parted /dev/sda unit s print</command> + <prompt>#</prompt> <command>parted /dev/sda unit s print</command> Model: ATA ST9320328CS (scsi) Disk /dev/sda: 625142448s Sector size (logical/physical): 512B/512B @@ -166,7 +167,7 @@ Number Start End Size File system Name <para> After resizing, the filesystem is marked as <emphasis>dirty</emphasis> so it will be checked on the next Windows boot. Clear this flag so that we can run further commands. <screen> -# <command>ntfsfix -d /dev/sda5</command> + <prompt>#</prompt><command>ntfsfix -d /dev/sda5</command> Mounting volume... OK Processing of $MFT and $MFTMirr completed successfully. Checking the alternate boot sector... OK @@ -178,7 +179,7 @@ NTFS partition /dev/sda5 was processed successfully. <listitem> <para>Find the cluster size and number of clusters. <screen> -# <command>ntfsinfo -m /dev/sda5|grep Cluster</command> + <prompt>#</prompt> <command>ntfsinfo -m /dev/sda5|grep Cluster</command> Cluster Size: 4096 Volume Size in Clusters: 9765624 Compression Block Clusters: 0 @@ -219,18 +220,18 @@ NTFS partition /dev/sda5 was processed successfully. <para> Use parted to resize the <systemitem class="filesystem">ntfs</systemitem> filesystem on <filename>/dev/sda</filename>. Using the <literal>s</literal> after the number ensures <command>parted</command> uses sectors as the unit. <screen> - <command># parted /dev/sda</command> + <prompt>#</prompt> <command>parted /dev/sda</command> GNU Parted 3.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. -(parted) -(parted) rm 5 -(parted) mkpart +<prompt>(parted)</prompt> +<prompt>(parted)</prompt> rm 5 +<prompt>(parted)</prompt> mkpart Partition name? []? windowsdisk File system type? [ext2]? ntfs Start? 232384512s End? 310509504s -(parted) quit +<prompt>(parted)</prompt> quit </screen> </para> </step> @@ -238,7 +239,7 @@ End? 310509504s <para> Check the partition table to confirm the free space is available, and exit <command>parted</command>. <screen> -(parted) print free + <prompt>(parted)</prompt> print free Model: ATA ST9320328CS (scsi) Disk /dev/sda: 320GB Sector size (logical/physical): 512B/512B @@ -254,7 +255,7 @@ Number Start End Size File system Name Flags 5 119GB 159GB 40.0GB ntfs 159GB 215GB 56.2GB Free Space -(parted) quit + <prompt>(parted)</prompt> quit </screen> </para> </step> diff --git a/en-US/GRUB-configuration.xml b/en-US/GRUB-configuration.xml index 386f57b..34d606f 100644 --- a/en-US/GRUB-configuration.xml +++ b/en-US/GRUB-configuration.xml @@ -58,7 +58,7 @@ <para> With root permissions, open the file <filename>/etc/default/grub</filename>. <screen> - <command>nano /etc/default/grub</command> + <prompt>#</prompt> <command>nano /etc/default/grub</command> <computeroutput> GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" @@ -96,7 +96,7 @@ <para> For BIOS systems: <screen> - <command>grub2-mkconfig -o /boot/grub/grub2.cfg</command> + <prompt>#</prompt> <command>grub2-mkconfig -o /boot/grub/grub2.cfg</command> </screen> </para> </step> @@ -104,7 +104,7 @@ <para> For UEFI systems: <screen> - <command>grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg</command> + <prompt>#</prompt> <command>grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg</command> </screen> </para> </step> diff --git a/en-US/GRUB-reinstalling.xml b/en-US/GRUB-reinstalling.xml index 7f599c0..0a82071 100644 --- a/en-US/GRUB-reinstalling.xml +++ b/en-US/GRUB-reinstalling.xml @@ -21,7 +21,7 @@ </member> </simplelist> </para> - <section id="GRUB-reinstalling-mkconfig"> + <section id="GRUB-mkconfig"> <title>Refreshing GRUB configuration</title> <para> To recreate the GRUB configuration from a booted system, use the <command>grub2-mkconfig</command> utility. The program will scan your system and create menu entries for what it finds. You should also use <command>grub2-mkconfig</command> after customizing menu entries, a process described in <xref linkend="GRUB-configuration" /> @@ -29,15 +29,13 @@ <para> Refresh GRUB configuration on a BIOS system: <screen> - <command>grub2-mkconfig -o /boot/grub2/grub.cfg</command> + <prompt>#</prompt> <command>grub2-mkconfig -o /boot/grub2/grub.cfg</command> </screen> </para> <para> Refresh GRUB configuration on UEFI systems: <screen> - <command> - grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg - </command> + <prompt>#</prompt><command>grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg</command> </screen> </para> </section> diff --git a/en-US/GRUB-runtime.xml b/en-US/GRUB-runtime.xml index 22689c9..d28854f 100644 --- a/en-US/GRUB-runtime.xml +++ b/en-US/GRUB-runtime.xml @@ -21,9 +21,9 @@ One of the default menu entries for Fedora is a <literal>rescue</literal> entry. This will load the same Fedora environment as the other entries, but loads a full <systemitem class="filesystem">initramfs</systemitem>. </para> <para> - The rescue option is useful if you have problems after adding new hardware. You can use the rescue option to regenerate the <systemitem class="filesystem">initramfs</systemitem> for all boot entries using this command, executed with root privileges: + The rescue option is useful if you have problems after adding new hardware. You can use the rescue option to regenerate the <systemitem class="filesystem">initramfs</systemitem> for all boot entries using this command: <screen> - <command>dracut --regenerate-all --force</command> + <prompt>#</prompt> <command>dracut --regenerate-all --force</command> </screen> </para> </note> diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml index b937bab..383c249 100644 --- a/en-US/Introduction.xml +++ b/en-US/Introduction.xml @@ -48,7 +48,7 @@ </screen> </para> <para> - The <literal>root prompt</literal> is always a hash ( # ) and a normal user prompt is always a dollar sign ( $ ). + The <literal>root prompt</literal> is always a hash ( # ) and a normal user prompt is always a dollar sign ( $ ). Example commands in this guide will include one of these prompts to show the privileges required for the action. </para> <para> <emphasis>To keep your system healthy and safe, do not execute user applications as root or log into a desktop environment as root.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits October 2014