| 1 |
nightmorph 08/03/05 08:26:01 |
| 2 |
|
| 3 |
Modified: gentoo-upgrading.xml |
| 4 |
Log: |
| 5 |
fix some english, some typos, etc. no content change. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.39 xml/htdocs/doc/en/gentoo-upgrading.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml?rev=1.39&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml?rev=1.39&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml?r1=1.38&r2=1.39 |
| 13 |
|
| 14 |
Index: gentoo-upgrading.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v |
| 17 |
retrieving revision 1.38 |
| 18 |
retrieving revision 1.39 |
| 19 |
diff -u -r1.38 -r1.39 |
| 20 |
--- gentoo-upgrading.xml 5 Mar 2008 08:23:59 -0000 1.38 |
| 21 |
+++ gentoo-upgrading.xml 5 Mar 2008 08:26:01 -0000 1.39 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.38 2008/03/05 08:23:59 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.39 2008/03/05 08:26:01 nightmorph Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/gentoo-upgrading.xml"> |
| 29 |
<title>Gentoo Upgrading Guide</title> |
| 30 |
@@ -69,22 +69,22 @@ |
| 31 |
|
| 32 |
<p> |
| 33 |
A recurring question about the Gentoo release process is: "Why roll out new |
| 34 |
-releases frequently, if they are not intended to let users update software?". |
| 35 |
+releases frequently, if they are not intended to let users update software?" |
| 36 |
There are various reasons: |
| 37 |
</p> |
| 38 |
|
| 39 |
<ul> |
| 40 |
<li> |
| 41 |
- A new release means new Installation CDs with bugfixes and more features. |
| 42 |
+ A new release means new Installation CDs with bugfixes and more features |
| 43 |
</li> |
| 44 |
<li> |
| 45 |
A new release provides an updated set of GRP packages, so that users that |
| 46 |
choose "the fast way" to install (stage3 + precompiled packages) end up |
| 47 |
- with a system that is not outdated. |
| 48 |
+ with a system that is not outdated |
| 49 |
</li> |
| 50 |
<li> |
| 51 |
Finally, a new release may, from time to time, implement some features that |
| 52 |
- are incompatible with previous releases. |
| 53 |
+ are incompatible with previous releases |
| 54 |
</li> |
| 55 |
</ul> |
| 56 |
|
| 57 |
@@ -117,7 +117,7 @@ |
| 58 |
along with the current ones, but they are marked as deprecated. When that |
| 59 |
happens a file named <path>deprecated</path> is put in the profile directory. |
| 60 |
The content of this file is the name of the profile that should be "upgraded |
| 61 |
-to"; portage uses this information to automatically warn you when you should |
| 62 |
+to"; Portage uses this information to automatically warn you when you should |
| 63 |
update to a new profile. |
| 64 |
</p> |
| 65 |
|
| 66 |
@@ -140,8 +140,8 @@ |
| 67 |
<body> |
| 68 |
|
| 69 |
<p> |
| 70 |
-If a new Gentoo release is announced that does not include a new profile |
| 71 |
-then you can safely pretend that it never happened :). |
| 72 |
+If a new Gentoo release does not include a new profile then you can safely |
| 73 |
+pretend that it never happened. :) |
| 74 |
</p> |
| 75 |
|
| 76 |
<p> |
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
-- |
| 81 |
gentoo-doc-cvs@l.g.o mailing list |
Archives