Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit f5bc0c1

Browse files
committed
[po] auto sync bot
1 parent ededfc9 commit f5bc0c1

8 files changed

Lines changed: 80 additions & 54 deletions

File tree

bugs.po

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,16 @@
44
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
55
#
66
# Translators:
7-
# zkonge, 2017
87
# chordy <[email protected]>, 2017
9-
# Junkai Shao <[email protected]>, 2017
108
# Thomas ZHANG <[email protected]>, 2017
11-
# Larry Wang <[email protected]>, 2017
129
# 操旭 <[email protected]>, 2017
13-
# eric R <[email protected]>, 2017
10+
# Shengjing Zhu <[email protected]>, 2018
11+
# eric R <[email protected]>, 2018
1412
# hanfeng <[email protected]>, 2018
15-
# Shengjing Zhu <[email protected]>, 2019
13+
# Junkai Shao <[email protected]>, 2018
14+
# Larry Wang <[email protected]>, 2018
15+
# zkonge, 2018
16+
# Freesand Leo <[email protected]>, 2019
1617
#
1718
#, fuzzy
1819
msgid ""
@@ -21,7 +22,7 @@ msgstr ""
2122
"Report-Msgid-Bugs-To: \n"
2223
"POT-Creation-Date: 2019-01-10 10:19+0900\n"
2324
"PO-Revision-Date: 2017-02-16 17:31+0000\n"
24-
"Last-Translator: Shengjing Zhu <zsj950618@gmail.com>, 2019\n"
25+
"Last-Translator: Freesand Leo <yuqinju@163.com>, 2019\n"
2526
"Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
2627
"MIME-Version: 1.0\n"
2728
"Content-Type: text/plain; charset=UTF-8\n"
@@ -46,8 +47,8 @@ msgid ""
4647
"Python as it streamlines the process and involves less people. Learn how to "
4748
":ref:`contribute <contributing-to-python>`."
4849
msgstr ""
49-
"有时候自己修复漏洞并将补丁提交给 Python 会更快,因为它简化了流程并且减少了参与的人力。学习如何提交补丁,请参考 :ref:`contribute"
50-
" <contributing-to-python>`。"
50+
"有时候自己修复漏洞并将补丁提交给 Python 会更快,因为它简化了流程并且减少了参与的人力。学习如何提交补丁,请参考 :ref:`提供修正 "
51+
"<contributing-to-python>`。"
5152

5253
#: ../../bugs.rst:16
5354
msgid "Documentation bugs"
@@ -59,8 +60,8 @@ msgid ""
5960
"improvement, please submit a bug report on the :ref:`tracker <using-the-"
6061
"tracker>`. If you have a suggestion on how to fix it, include that as well."
6162
msgstr ""
62-
"如果您在本文档中发现了错误并打算帮助我们改进,请将错误提交到 :ref:`tracker <using-the-tracker>`。 "
63-
"如果您有相应的修正建议,请一并提交。如果是翻译相关的错误,请务必提交到 https://github.com/python/python-docs-"
63+
"如果您在本文档中发现了错误并打算帮助我们改进,请将错误提交到 :ref:`追踪系统 <using-the-tracker>`。 "
64+
"如果您有相应的修正建议,请一并提交。 如果是翻译相关的错误,请务必提交到 https://github.com/python/python-docs-"
6465
"zh-cn/issues。如果将翻译问题反馈到了其他地方,可能会因为语言不通而不能及时处理。"
6566

6667
#: ../../bugs.rst:22

c-api/capsule.po

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
#
66
# Translators:
77
# Shengjing Zhu <[email protected]>, 2019
8-
# RSNOW <[email protected]>, 2019
98
# Trim21 <[email protected]>, 2019
9+
# RSNOW <[email protected]>, 2019
1010
#
1111
#, fuzzy
1212
msgid ""
@@ -15,7 +15,7 @@ msgstr ""
1515
"Report-Msgid-Bugs-To: \n"
1616
"POT-Creation-Date: 2019-01-01 10:14+0900\n"
1717
"PO-Revision-Date: 2017-02-16 17:33+0000\n"
18-
"Last-Translator: Trim21 <[email protected]>, 2019\n"
18+
"Last-Translator: RSNOW <[email protected]>, 2019\n"
1919
"Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
2020
"MIME-Version: 1.0\n"
2121
"Content-Type: text/plain; charset=UTF-8\n"
@@ -57,7 +57,7 @@ msgstr "参阅 :c:func:`PyCapsule_New` 来获取 PyCapsule_Destructor 返回值
5757

5858
#: ../../c-api/capsule.rst:37
5959
msgid "Return true if its argument is a :c:type:`PyCapsule`."
60-
msgstr ""
60+
msgstr "如果参数是一个 :c:type:`PyCapsule` 则返回 True"
6161

6262
#: ../../c-api/capsule.rst:42
6363
msgid ""

howto/sockets.po

Lines changed: 31 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,9 @@
77
# Fei Yin <[email protected]>, 2018
88
# Junkai Shao <[email protected]>, 2018
99
# ww song <[email protected]>, 2018
10+
# Freesand Leo <[email protected]>, 2018
1011
# keelii <[email protected]>, 2019
11-
# Freesand Leo <yuqinju@163.com>, 2019
12+
# Meng Du <alphanow@gmail.com>, 2019
1213
#
1314
#, fuzzy
1415
msgid ""
@@ -17,7 +18,7 @@ msgstr ""
1718
"Report-Msgid-Bugs-To: \n"
1819
"POT-Creation-Date: 2019-01-01 10:14+0900\n"
1920
"PO-Revision-Date: 2017-02-16 17:46+0000\n"
20-
"Last-Translator: Freesand Leo <yuqinju@163.com>, 2019\n"
21+
"Last-Translator: Meng Du <alphanow@gmail.com>, 2019\n"
2122
"Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
2223
"MIME-Version: 1.0\n"
2324
"Content-Type: text/plain; charset=UTF-8\n"
@@ -50,7 +51,7 @@ msgid ""
5051
"a lot of them), but I hope it will give you enough background to begin using"
5152
" them decently."
5253
msgstr ""
53-
"套接字几乎无处不在,但是它却是被误解最严重的技术之一。这是一篇简单的套接字概述。并不是一篇真正的教程 - "
54+
"套接字几乎无处不在,但是它却是被误解最严重的技术之一。这是一篇简单的套接字概述。并不是一篇真正的教程 —— "
5455
"你需要做更多的事情才能让它工作起来。其中也并没有涵盖细节(细节会有很多),但是我希望它能提供足够的背景知识,让你像模像样的开始使用套接字"
5556

5657
#: ../../howto/sockets.rst:20
@@ -244,10 +245,10 @@ msgid ""
244245
"reply. Without a ``flush`` in there, you may wait forever for the reply, "
245246
"because the request may still be in your output buffer."
246247
msgstr ""
247-
"现在有两组用于通信的动词。你可以使用 ``send`` 和 ``recv``,或者你可以把客户端套接字改成文件类型的怪东西来使用 ``read`` 和"
248-
" ``write`` 方法。后者是 Java 语言中表示套接字的方法,在这儿我将不会讨论这个,但是要提醒你需要调用套接字的 ``flush`` "
249-
"方法,这些是缓冲区的文件,一个经常出现的错误是 ``write`` 一些东西,然后不调用 ``flush`` 就开始 ``read`` "
250-
"一个响应,你可能会为了这个响应一直等待,因为请求可能还在你的输出缓冲中。"
248+
"现在有两组用于通信的动词。你可以使用 ``send`` 和 ``recv`` ,或者你可以把客户端套接字改成文件类型的形式来使用 ``read`` 和"
249+
" ``write`` 方法。后者是 Java 语言中表示套接字的方法,我将不会在这儿讨论这个,但是要提醒你需要调用套接字的 ``flush`` "
250+
"方法。这些是“缓冲”的文件,一个经常出现的错误是 ``write`` 一些东西,然后就直接开始 ``read`` 一个响应。如果不调用 "
251+
"``flush`` ,你可能会一直等待这个响应,因为请求可能还在你的输出缓冲中。"
251252

252253
#: ../../howto/sockets.rst:152
253254
msgid ""
@@ -314,9 +315,9 @@ msgid ""
314315
"gets more complex. (And in C, it's not much worse, except you can't use "
315316
"``strlen`` if the message has embedded ``\\0``\\ s.)"
316317
msgstr ""
317-
"发送分部代码几乎可用于任何消息传递方案 - 在 Python 中你发送字符串,可以使用 ``len()`` 方法来确定它的长度(即使它嵌入了 ``\\ "
318-
"0`` 字符)主要是接收代码变得更复杂。(在 C 语言中,并没有太糟糕,除非消息嵌入了 ``\\ 0`` 字符而且你又无法使用 ``strlen`` "
319-
")"
318+
"发送分部代码几乎可用于任何消息传递方案 —— 在 Python 中你发送字符串,可以使用 ``len()`` 方法来确定它的长度(即使它嵌入了 "
319+
"``\\0`` 字符)主要是接收代码变得更复杂。(在 C 语言中,并没有更糟糕,除非消息嵌入了 ``\\0`` 字符而且你又无法使用 "
320+
"``strlen`` )"
320321

321322
#: ../../howto/sockets.rst:223
322323
msgid ""
@@ -328,8 +329,8 @@ msgid ""
328329
"chunk size, (4096 or 8192 is frequently a good match for network buffer "
329330
"sizes), and scanning what you've received for a delimiter."
330331
msgstr ""
331-
"最简单的改进是让消息的第一个字符表示消息类型,由类型决定长度。现在你需要两次 ``recv`` - "
332-
"第一次取首字符来知晓长度,第二次在循环中获取剩余所有的消息。如果你决定到分界线,你将收到一些任意大小的块,(4096 或者 8192 "
332+
"最简单的改进是让消息的第一个字符表示消息类型,由类型决定长度。现在你需要两次 ``recv``\\ - "
333+
"第一次取(至少)第一个字符来知晓长度,第二次在循环中获取剩余所有的消息。如果你决定到分界线,你将收到一些任意大小的块,(4096 或者 8192 "
333334
"通常是比较合适的网络缓冲区大小),扫描你接收到的分界符"
334335

335336
#: ../../howto/sockets.rst:231
@@ -354,17 +355,17 @@ msgid ""
354355
"not always manage to get rid of everything in one pass. And despite having "
355356
"read this, you will eventually get bit by it!"
356357
msgstr ""
357-
"用消息的长度做为消息的前缀(比如说,5个数字字符)会更复杂,因为,你可能在一次 ``recv`` 中没法取完这 5 "
358-
"个字符,为了能把程序跑起来,你将设法避免这种情况;但是在高负载的网络中,除非你使用两个``recv`` 循环 - "
359-
"第一个用来确定消息长度,第二个用来获取消息体的数据,否则你的代码会很快中断。真讨厌,这也是当你发现 ``send`` "
360-
"方法并不总是在一个地方处理所有的东西的感觉。尽管你读过这篇文章,但最终还是会有所了解"
358+
"以其长度(例如,作为5个数字字符)作为消息前缀时会变得更复杂,因为(信不信由你)你可能无法在一个 ``recv`` "
359+
"中获得所有5个字符。在一般使用时,你会侥幸避免该状况;但是在高网络负载中,除非你使用两个 ``recv`` 循环,否则你的代码将很快中断 —— "
360+
"第一个用于确定长度,第二个用于获取消息的数据部分。这很讨厌。当你发现 ``send`` 并不总是设法在支持搞定一切时,你也会有这种感觉。 "
361+
"尽管已经阅读过这篇文章,但最终还是会有所了解"
361362

362363
#: ../../howto/sockets.rst:246
363364
msgid ""
364365
"In the interests of space, building your character, (and preserving my "
365366
"competitive position), these enhancements are left as an exercise for the "
366367
"reader. Lets move on to cleaning up."
367-
msgstr "限于篇幅,建立你的角色,(保持与我的竞争位置),这些改进将留给读者做为练习。让我们继续。"
368+
msgstr "限于篇幅,建立你的角色,(保持与我的竞争位置),这些改进将留给读者做为练习。现在让我们继续。"
368369

369370
#: ../../howto/sockets.rst:252
370371
msgid "Binary Data"
@@ -382,7 +383,7 @@ msgid ""
382383
"network order is host order, these do nothing, but where the machine is "
383384
"byte-reversed, these swap the bytes around appropriately."
384385
msgstr ""
385-
"通过套接字传送二进制数据是可能的。主要问题在于并非所有机器都用同样的二进制数据格式。比如 Motorola 芯片用两个十六进制字节 00 01 "
386+
"通过套接字传送二进制数据是可行的。主要问题在于并非所有机器都用同样的二进制数据格式。比如 Motorola 芯片用两个十六进制字节 00 01 "
386387
"来表示一个 16 位整数值 1。而 Intel 和 DEC 则会做字节反转 —— 即用 01 00 来表示 1。套接字库要求转换 16 位和 32 "
387388
"位整数 —— ``ntohl, htonl, ntohs, htons`` 其中的「n」表示 *network*,「h」表示 *host*,「s」表示 "
388389
"*short*,「l」表示 *long*。在网络序列就是主机序列时它们什么都不做,但是如果机器是字节反转的则会适当地交换字节序。"
@@ -413,10 +414,9 @@ msgid ""
413414
"same as ``shutdown(); close()``. So in most situations, an explicit "
414415
"``shutdown`` is not needed."
415416
msgstr ""
416-
"严格地讲,你应该在 ``close`` 它之前将套接字 ``shutdown``。 ``shutdown`` 是套接字另一端的一种建议。 "
417-
"调用时参数不同意义也不一样,它可能意味着「我不会再发送了,但我仍然会监听」,或者「我没有监听了,真棒!」。 "
418-
"然而,大多数套接字库或者程序员都习惯了忽略使用这种礼节,因为通常情况下 ``close`` 与 ``shutdown(); close();`` "
419-
"是一样的。所以在大多数情况下,不需要显式的 ``shutdown``。"
417+
"严格地讲,你应该在 ``close`` 它之前将套接字 ``shutdown`` 。 ``shutdown`` "
418+
"是发送给套接字另一端的一种建议。调用时参数不同意义也不一样,它可能意味着「我不会再发送了,但我仍然会监听」,或者「我没有监听了,真棒!」。然而,大多数套接字库或者程序员都习惯了忽略使用这种礼节,因为通常情况下"
419+
" ``close`` 与 ``shutdown(); close()`` 是一样的。所以在大多数情况下,不需要显式的 ``shutdown`` 。"
420420

421421
#: ../../howto/sockets.rst:282
422422
msgid ""
@@ -427,6 +427,9 @@ msgid ""
427427
"complete request. The server sends a reply. If the ``send`` completes "
428428
"successfully then, indeed, the client was still receiving."
429429
msgstr ""
430+
"高效使用 ``shutdown`` 的一种方法是在类似 HTTP 的交换中。客户端发送请求,然后执行 ``shutdown(1)`` 。 "
431+
"这告诉服务器“此客户端已完成发送,但仍可以接收”。服务器可以通过接收 0 字节来检测 “EOF” 。它可以假设它有完整的请求。服务器发送回复。如果 "
432+
"``send`` 成功完成,那么客户端仍在接收。"
430433

431434
#: ../../howto/sockets.rst:289
432435
msgid ""
@@ -437,6 +440,9 @@ msgid ""
437440
"indefinitely, thinking you're just being slow. *Please* ``close`` your "
438441
"sockets when you're done."
439442
msgstr ""
443+
"Python 进一步自动关闭,并说当一个套接字被垃圾收集时,如果需要它会自动执行 ``close`` "
444+
"。但依靠这个机制是一个非常坏的习惯。如果你的套接字在没有 ``close`` "
445+
"的情况下就消失了,那么另一端的套接字可能会无限期地挂起,以为你只是慢了一步。完成后 *请* ``close`` 你的套接字。"
440446

441447
#: ../../howto/sockets.rst:297
442448
msgid "When Sockets Die"
@@ -456,6 +462,9 @@ msgid ""
456462
" automatic recycling of resources. In other words, if you do manage to kill "
457463
"the thread, your whole process is likely to be screwed up."
458464
msgstr ""
465+
"使用阻塞套接字最糟糕的事情可能就是当另一边下线时(没有 ``close`` )会发生什么。你的套接字可能会挂起。 TCP "
466+
"是一种可靠的协议,它会在放弃连接之前等待很长时间。如果你正在使用线程,那么整个线程基本上已经死了。你无能为力。只要你没有做一些愚蠢的事情,比如在进行阻塞读取时持有一个锁,那么线程并没有真正消耗掉资源。"
467+
" *不要* 尝试杀死线程 —— 线程比进程更有效的部分原因是它们避免了与自动回收资源相关的开销。换句话说,如果你设法杀死线程,你的整个进程很可能被搞坏。"
459468

460469
#: ../../howto/sockets.rst:313
461470
msgid "Non-blocking Sockets"

library/asyncio-eventloop.po

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -574,7 +574,7 @@ msgstr ""
574574
#: ../../library/asyncio-eventloop.rst:511
575575
#: ../../library/asyncio-eventloop.rst:664
576576
msgid "The *ssl_handshake_timeout* parameter."
577-
msgstr ""
577+
msgstr "*ssl_handshake_timeout* 形参。"
578578

579579
#: ../../library/asyncio-eventloop.rst:413
580580
#: ../../library/asyncio-eventloop.rst:594

library/asyncio-stream.po

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@
55
#
66
# Translators:
77
# Fred <[email protected]>, 2018
8-
# Freesand Leo <[email protected]>, 2018
98
# Meng Du <[email protected]>, 2019
109
# walkinrain <[email protected]>, 2019
1110
# kevin wong <[email protected]>, 2019
11+
# Freesand Leo <[email protected]>, 2019
1212
#
1313
#, fuzzy
1414
msgid ""
@@ -17,7 +17,7 @@ msgstr ""
1717
"Report-Msgid-Bugs-To: \n"
1818
"POT-Creation-Date: 2019-01-01 10:14+0900\n"
1919
"PO-Revision-Date: 2017-02-16 17:49+0000\n"
20-
"Last-Translator: kevin wong <huagang517@126.com>, 2019\n"
20+
"Last-Translator: Freesand Leo <yuqinju@163.com>, 2019\n"
2121
"Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
2222
"MIME-Version: 1.0\n"
2323
"Content-Type: text/plain; charset=UTF-8\n"
@@ -59,14 +59,14 @@ msgstr "下面的高级 asyncio 函数可以用来创建和处理流:"
5959
msgid ""
6060
"Establish a network connection and return a pair of ``(reader, writer)`` "
6161
"objects."
62-
msgstr "建立网络连接并返回一对' ``(reader, writer)`` 对象。"
62+
msgstr "建立网络连接并返回一对 ``(reader, writer)`` 对象。"
6363

6464
#: ../../library/asyncio-stream.rst:54
6565
msgid ""
6666
"The returned *reader* and *writer* objects are instances of "
6767
":class:`StreamReader` and :class:`StreamWriter` classes."
6868
msgstr ""
69-
"返回的 *reader* 和 *writer* 对象是 :class:`StreamReader` 和 :class: `StreamWriter` "
69+
"返回的 *reader* 和 *writer* 对象是 :class:`StreamReader` 和 :class:`StreamWriter` "
7070
"类的实例。"
7171

7272
#: ../../library/asyncio-stream.rst:57
@@ -90,11 +90,11 @@ msgstr "其余的参数直接传递到 :meth:`loop.create_connection` 。"
9090

9191
#: ../../library/asyncio-stream.rst:69 ../../library/asyncio-stream.rst:122
9292
msgid "The *ssl_handshake_timeout* parameter."
93-
msgstr ""
93+
msgstr "*ssl_handshake_timeout* 形参。"
9494

9595
#: ../../library/asyncio-stream.rst:79
9696
msgid "Start a socket server."
97-
msgstr ""
97+
msgstr "启动套接字服务。"
9898

9999
#: ../../library/asyncio-stream.rst:81
100100
msgid ""

library/dataclasses.po

Lines changed: 17 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -713,6 +713,8 @@ msgid ""
713713
"arguments when a default value for the field is needed. For example, to "
714714
"create a new instance of a list, use::"
715715
msgstr ""
716+
"如果一个 :func:`field` 指定了一个 ``default_factory`` "
717+
",当需要该字段的默认值时,将使用零参数调用它。例如,要创建列表的新实例,请使用::"
716718

717719
#: ../../library/dataclasses.rst:521
718720
msgid ""
@@ -721,30 +723,33 @@ msgid ""
721723
"will always be called from the generated :meth:`__init__` function. This "
722724
"happens because there is no other way to give the field an initial value."
723725
msgstr ""
726+
"如果一个字段被排除在 :meth:`__init__` 之外(使用 ``init=False`` )并且字段也指定 "
727+
"``default_factory`` ,则默认的工厂函数将始终从生成的 :meth:`__ init__` "
728+
"函数调用。发生这种情况是因为没有其他方法可以为字段提供初始值。"
724729

725730
#: ../../library/dataclasses.rst:528
726731
msgid "Mutable default values"
727-
msgstr ""
732+
msgstr "可变的默认值"
728733

729734
#: ../../library/dataclasses.rst:530
730735
msgid ""
731736
"Python stores default member variable values in class attributes. Consider "
732737
"this example, not using dataclasses::"
733-
msgstr ""
738+
msgstr "Python 在类属性中存储默认成员变量值。思考这个例子,不使用数据类::"
734739

735740
#: ../../library/dataclasses.rst:545
736741
msgid ""
737742
"Note that the two instances of class ``C`` share the same class variable "
738743
"``x``, as expected."
739-
msgstr ""
744+
msgstr "请注意,类 ``C`` 的两个实例共享相同的类变量 ``x`` ,如预期的那样。"
740745

741746
#: ../../library/dataclasses.rst:548
742747
msgid "Using dataclasses, *if* this code was valid::"
743-
msgstr ""
748+
msgstr "使用数据类, *如果* 此代码有效::"
744749

745750
#: ../../library/dataclasses.rst:556
746751
msgid "it would generate code similar to::"
747-
msgstr ""
752+
msgstr "它生成的代码类似于::"
748753

749754
#: ../../library/dataclasses.rst:567
750755
msgid ""
@@ -757,12 +762,16 @@ msgid ""
757762
" a default parameter of type ``list``, ``dict``, or ``set``. This is a "
758763
"partial solution, but it does protect against many common errors."
759764
msgstr ""
765+
"这与使用类 ``C`` 的原始示例具有相同的问题。也就是说,在创建类实例时没有为 ``x`` 指定值的类 ``D`` 的两个实例将共享相同的 ``x``"
766+
" 副本。由于数据类只使用普通的 Python 类创建,因此它们也会共享此行为。数据类没有通用的方法来检测这种情况。相反,如果数据类检测到类型为 "
767+
"``list`` 、 ``dict`` 或 ``set`` 的默认参数,则会引发 :exc:`TypeError` "
768+
"。这是一个部分解决方案,但它可以防止许多常见错误。"
760769

761770
#: ../../library/dataclasses.rst:577
762771
msgid ""
763772
"Using default factory functions is a way to create new instances of mutable "
764773
"types as default values for fields::"
765-
msgstr ""
774+
msgstr "使用默认工厂函数是一种创建可变类型新实例的方法,并将其作为字段的默认值::"
766775

767776
#: ../../library/dataclasses.rst:587
768777
msgid "Exceptions"
@@ -773,3 +782,5 @@ msgid ""
773782
"Raised when an implicitly defined :meth:`__setattr__` or :meth:`__delattr__`"
774783
" is called on a dataclass which was defined with ``frozen=True``."
775784
msgstr ""
785+
"在使用 ``frozen=True`` 定义的数据类上调用隐式定义的 :meth:`__setattr__` 或 "
786+
":meth:`__delattr__`时引发。"

0 commit comments

Comments
 (0)