Searched full:phrase (Results 1 – 25 of 117) sorted by relevance
12345
| /kernel/linux/linux-5.10/Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 471 Subject: [PATCH 001/123] subsystem: summary phrase
499 電子メールのサブジェクトの「summary phrase」はそのパッチの概要を正確
500 に表現しなければなりません。「summary phrase」をファイル名にしてはい
501 けません。パッチシリーズ中でそれぞれのパッチは同じ「summary phrase」を
505 あなたの電子メールの「summary phrase」がそのパッチにとって世界で唯一の識別子に
506 なるように心がけてください。「summary phrase」は git のチェンジログの中へ
507 ずっと伝播していきます。「summary phrase」は、開発者が後でパッチを参照する
509 人々はそのパッチに関連した議論を読むために「summary phrase」を使って google で
514 これらの理由のため、「summary phrase」はなぜパッチが必要であるか、パッチが何を
516 「summary phrase」は簡潔であり説明的である表現を目指しつつ、うまく
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 472 Subject: [PATCH 001/123] subsystem: summary phrase
500 電子メールのサブジェクトの「summary phrase」はそのパッチの概要を正確
501 に表現しなければなりません。「summary phrase」をファイル名にしてはい
502 けません。パッチシリーズ中でそれぞれのパッチは同じ「summary phrase」を
506 あなたの電子メールの「summary phrase」がそのパッチにとって世界で唯一の識別子に
507 なるように心がけてください。「summary phrase」は git のチェンジログの中へ
508 ずっと伝播していきます。「summary phrase」は、開発者が後でパッチを参照する
510 人々はそのパッチに関連した議論を読むために「summary phrase」を使って google で
515 これらの理由のため、「summary phrase」はなぜパッチが必要であるか、パッチが何を
517 「summary phrase」は簡潔であり説明的である表現を目指しつつ、うまく
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | submitting-patches.rst | 558 Subject: [PATCH 001/123] subsystem: summary phrase
587 The ``summary phrase`` in the email's Subject should concisely
589 phrase`` should not be a filename. Do not use the same ``summary
590 phrase`` for every patch in a whole patch series (where a ``patch
593 Bear in mind that the ``summary phrase`` of your email becomes a
595 into the ``git`` changelog. The ``summary phrase`` may later be used in
597 google for the ``summary phrase`` to read discussion regarding that
609 The ``summary phrase`` may be prefixed by tags enclosed in square
610 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
611 not considered part of the summary phrase, but describe how the patch
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | submitting-patches.rst | 615 Subject: [PATCH 001/123] subsystem: summary phrase
644 The ``summary phrase`` in the email's Subject should concisely
646 phrase`` should not be a filename. Do not use the same ``summary
647 phrase`` for every patch in a whole patch series (where a ``patch
650 Bear in mind that the ``summary phrase`` of your email becomes a
652 into the ``git`` changelog. The ``summary phrase`` may later be used in
654 google for the ``summary phrase`` to read discussion regarding that
666 The ``summary phrase`` may be prefixed by tags enclosed in square
667 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
668 not considered part of the summary phrase, but describe how the patch
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/it_IT/process/ |
| D | submitting-patches.rst | 610 Subject: [PATCH 001/123] subsystem: summary phrase
640 La ``summary phrase`` nell'oggetto dell'email dovrebbe descrivere brevemente
641 il contenuto della patch. La ``summary phrase`` non dovrebbe essere un nome
642 di file. Non utilizzate la stessa ``summary phrase`` per tutte le patch in
646 Ricordatevi che la ``summary phrase`` della vostra email diventerà un
648 changelog ``git``. La ``summary phrase`` potrà essere usata in futuro
650 cercare la ``summary phrase`` su internet per leggere le discussioni che la
660 La ``summary phrase`` può avere un'etichetta (*tag*) di prefisso racchiusa fra
661 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>".
704 venga trovata. Come nella ``summary phrase``, è importante essere sia
|
| /kernel/linux/linux-5.10/Documentation/translations/it_IT/process/ |
| D | submitting-patches.rst | 683 Subject: [PATCH 001/123] subsystem: summary phrase
713 La ``summary phrase`` nell'oggetto dell'email dovrebbe descrivere brevemente
714 il contenuto della patch. La ``summary phrase`` non dovrebbe essere un nome
715 di file. Non utilizzate la stessa ``summary phrase`` per tutte le patch in
719 Ricordatevi che la ``summary phrase`` della vostra email diventerà un
721 changelog ``git``. La ``summary phrase`` potrà essere usata in futuro
723 cercare la ``summary phrase`` su internet per leggere le discussioni che la
733 La ``summary phrase`` può avere un'etichetta (*tag*) di prefisso racchiusa fra
734 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>".
768 che la vostra patch venga trovata. Come nella ``summary phrase``, è importante
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,mvebu-pinctrl.txt | 9 phrase "pin configuration node".
|
| D | pinctrl-rk805.txt | 7 including the meaning of the phrase "pin configuration node".
|
| D | pinctrl-vt8500.txt | 21 phrase "pin configuration node".
|
| D | lantiq,pinctrl-falcon.txt | 10 phrase "pin configuration node".
|
| D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
|
| D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | qcom,ipq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,mvebu-pinctrl.txt | 9 phrase "pin configuration node".
|
| D | pinctrl-rk805.txt | 7 including the meaning of the phrase "pin configuration node".
|
| D | pinctrl-vt8500.txt | 21 phrase "pin configuration node".
|
| D | lantiq,pinctrl-falcon.txt | 10 phrase "pin configuration node".
|
| D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
|
| D | qcom,msm8660-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | qcom,ipq8064-pinctrl.txt | 24 phrase "pin configuration node".
|
| D | xlnx,zynq-pinctrl.txt | 10 phrase "pin configuration node".
|
| D | brcm,bcm2835-gpio.txt | 37 phrase "pin configuration node".
|
| D | nvidia,tegra194-pinmux.txt | 11 phrase "pin configuration node".
|
| D | fsl,imx-pinctrl.txt | 12 phrase "pin configuration node".
|
12345