From: "Sven Vermeulen (swift)" <swift@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-disk.xml
Date: Tue, 31 Dec 2013 20:37:40 +0000 (UTC) [thread overview]
Message-ID: <20131231203740.929C52004C@flycatcher.gentoo.org> (raw)
swift 13/12/31 20:37:40
Modified: hb-install-x86+amd64-disk.xml
Log:
Fix bug #496572 - Parted uses locations, not sizes
Revision Changes Path
1.38 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?rev=1.38&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?rev=1.38&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?r1=1.37&r2=1.38
Index: hb-install-x86+amd64-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- hb-install-x86+amd64-disk.xml 31 Dec 2013 20:34:17 -0000 1.37
+++ hb-install-x86+amd64-disk.xml 31 Dec 2013 20:37:40 -0000 1.38
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v 1.37 2013/12/31 20:34:17 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v 1.38 2013/12/31 20:37:40 swift Exp $ -->
<sections>
@@ -13,7 +13,7 @@
This chapter describes how to partition a disk for future usage.
</abstract>
-<version>29</version>
+<version>30</version>
<date>2013-12-31</date>
<section>
@@ -479,7 +479,7 @@
<p>
Do the same for the boot partition (128 MB), swap partition (in the example,
512 MB) and the root partition that spans the remaining disk (for which the
-end size is marked as <c>-1</c>, meaning the end of the disk minus one MB,
+end location is marked as <c>-1</c>, meaning the end of the disk minus one MB,
which is the farthest a partition can go).
</p>
next reply other threads:[~2013-12-31 20:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 20:37 Sven Vermeulen (swift) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-23 19:43 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-disk.xml Sven Vermeulen (swift)
2013-12-31 20:43 Sven Vermeulen (swift)
2013-12-31 20:34 Sven Vermeulen (swift)
2013-12-31 20:33 Sven Vermeulen (swift)
2013-12-30 15:54 Sven Vermeulen (swift)
2013-12-29 11:20 Sven Vermeulen (swift)
2013-12-19 13:33 Sven Vermeulen (swift)
2013-12-18 15:01 Sven Vermeulen (swift)
2013-12-18 11:40 Sven Vermeulen (swift)
2013-12-17 10:09 Sven Vermeulen (swift)
2013-12-17 9:26 Sven Vermeulen (swift)
2013-12-17 9:13 Sven Vermeulen (swift)
2013-12-17 9:10 Sven Vermeulen (swift)
2013-04-11 18:25 Sven Vermeulen (swift)
2013-04-06 7:52 Sven Vermeulen (swift)
2011-08-23 17:31 Sven Vermeulen (swift)
2009-01-09 18:12 Xavier Neys (neysx)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131231203740.929C52004C@flycatcher.gentoo.org \
--to=swift@gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox