From: "Lukasz Damentko (rane)" <rane@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/pl: gnupg-user.xml mailfilter-guide.xml metadoc.xml
Date: Wed, 23 Jan 2008 17:17:37 +0000 [thread overview]
Message-ID: <E1JHjEH-0003Sc-Na@stork.gentoo.org> (raw)
rane 08/01/23 17:17:37
Modified: gnupg-user.xml mailfilter-guide.xml metadoc.xml
Log:
repodoc compliant
Revision Changes Path
1.14 xml/htdocs/doc/pl/gnupg-user.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/gnupg-user.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/gnupg-user.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/gnupg-user.xml?r1=1.13&r2=1.14
Index: gnupg-user.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/pl/gnupg-user.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- gnupg-user.xml 20 Jan 2008 20:11:41 -0000 1.13
+++ gnupg-user.xml 23 Jan 2008 17:17:37 -0000 1.14
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/gnupg-user.xml,v 1.13 2008/01/20 20:11:41 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/gnupg-user.xml,v 1.14 2008/01/23 17:17:37 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/pl/gnupg-user.xml" lang="pl">
@@ -921,9 +921,9 @@
Aby rozwiązać ten problem stworzone zostały Serwery Kluczy. Gdy się tworzy swoją
parę kluczy (Publiczny i Prywatny) wysyła się swój klucz publiczny do serwera.
Od tego momentu każdy może stamtąd otrzymać nasz klucz. To rozwiązuje problem
-znalezienia czyjegoś klucza. Ale skąd mam na pewno wiedzieć że klucz jest kluczem
-autora? Do tego musi powstać kolejne rozwiązanie i to jest właśnie podpisywanie
-kluczy:
+znalezienia czyjegoś klucza. Ale skąd mam na pewno wiedzieć że klucz jest
+kluczem autora? Do tego musi powstać kolejne rozwiązanie i to jest właśnie
+podpisywanie kluczy:
</p>
<p>
1.12 xml/htdocs/doc/pl/mailfilter-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/mailfilter-guide.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/mailfilter-guide.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/mailfilter-guide.xml?r1=1.11&r2=1.12
Index: mailfilter-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/pl/mailfilter-guide.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- mailfilter-guide.xml 17 Aug 2007 13:27:01 -0000 1.11
+++ mailfilter-guide.xml 23 Jan 2008 17:17:37 -0000 1.12
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/mailfilter-guide.xml,v 1.11 2007/08/17 13:27:01 shadoww Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/mailfilter-guide.xml,v 1.12 2008/01/23 17:17:37 rane Exp $ -->
<guide link="/doc/pl/mailfilter-guide.xml" lang="pl">
<title>Filtrowanie poczty w Gentoo</title>
@@ -821,7 +821,7 @@
<p>
Przejrzysty przedownik jak używać zestawów reguł SARE wraz z <c>sa-update</c>
-można znaleźć <uri
+można znaleźć <uri
link="http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt">tutaj</uri>.
</p>
1.230 xml/htdocs/doc/pl/metadoc.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/metadoc.xml?rev=1.230&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/metadoc.xml?rev=1.230&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/metadoc.xml?r1=1.229&r2=1.230
Index: metadoc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/pl/metadoc.xml,v
retrieving revision 1.229
retrieving revision 1.230
diff -u -r1.229 -r1.230
--- metadoc.xml 17 Jan 2008 19:55:20 -0000 1.229
+++ metadoc.xml 23 Jan 2008 17:17:37 -0000 1.230
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/metadoc.xml,v 1.229 2008/01/17 19:55:20 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/metadoc.xml,v 1.230 2008/01/23 17:17:37 rane Exp $ -->
<!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd">
<metadoc lang="pl" parent="/doc/en/metadoc.xml">
@@ -283,7 +283,7 @@
<file id="amd64-howtos">/proj/pl/base/amd64/howtos/index.xml</file>
<file id="amd64-howtos-bugs">/proj/pl/base/amd64/howtos/bugs.xml</file>
<file id="amd64-howtos-chroot">/proj/pl/base/amd64/howtos/chroot-old.xml</file>
- <file id="amd64-howtos-fpic">/proj/en/base/amd64/howtos/fpic-howto.xml</file>
+ <file id="amd64-howtos-fpic">/proj/pl/base/amd64/howtos/fpic-howto.xml</file>
<file id="gentoo-dev-handbook">/proj/pl/devrel/handbook/handbook.xml</file>
<file id="doc-policy">/proj/en/gdp/doc/doc-policy.xml</file>
<file id="doc-tipsntricks">/proj/pl/gdp/doc/doc-tipsntricks.xml</file>
--
gentoo-commits@lists.gentoo.org mailing list
reply other threads:[~2008-01-23 17:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1JHjEH-0003Sc-Na@stork.gentoo.org \
--to=rane@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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