neysx 07/05/24 09:47:47 Modified: gentoolkit.xml Log: #179617 Typo fix, thanks to Charles Clément
Revision Changes Path 1.28 xml/htdocs/doc/en/gentoolkit.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.28&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.28&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoolkit.xml?r1=1.27&r2=1.28 Index: gentoolkit.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- gentoolkit.xml 26 Mar 2007 21:21:00 -0000 1.27 +++ gentoolkit.xml 24 May 2007 09:47:47 -0000 1.28 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.27 2007/03/26 21:21:00 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.28 2007/05/24 09:47:47 neysx Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/gentoolkit.xml"> @@ -424,7 +424,7 @@ <p> We can also find out which ebuild is being used for a specific package using -<c>equery</c>. This is done my using the <c>equery which</c> command which +<c>equery</c>. This is done by using the <c>equery which</c> command which displays the full path to the ebuild. </p> -- [EMAIL PROTECTED] mailing list
