Merge branch 'driver-core-next' of...

And assuming 'dev' is the struct device passed into the probe hook, the driver

probe function would do something like:

	create_device(&mydriver_class, dev, chrdev, &private_data, "my_name");

	device_create(&mydriver_class, dev, chrdev, &private_data, "my_name");

Microsoft (namely ACPI) ensures that almost every device on almost any bus

on an x86-compatible system can work within this paradigm.  Of course,

not every bus is able to support all such operations, although most

buses support a most of those operations.

buses support most of those operations.

Downstream Access

struct pci_dev {

	...

	struct device dev;

	struct device dev;     /* Generic device interface */

	...

};

Note first that it is statically allocated. This means only one allocation on

device discovery. Note also that it is at the _end_ of struct pci_dev. This is

to make people think about what they're doing when switching between the bus

driver and the global driver; and to prevent against mindless casts between

the two.

Note first that the struct device dev within the struct pci_dev is

statically allocated. This means only one allocation on device discovery.

Note also that that struct device dev is not necessarily defined at the

front of the pci_dev structure.  This is to make people think about what

they're doing when switching between the bus driver and the global driver,

and to discourage meaningless and incorrect casts between the two.

The PCI bus layer freely accesses the fields of struct device. It knows about

the structure of struct pci_dev, and it should know the structure of struct

device. Individual PCI device drivers that have been converted to the current

driver model generally do not and should not touch the fields of struct device,

unless there is a strong compelling reason to do so.

unless there is a compelling reason to do so.

This abstraction is prevention of unnecessary pain during transitional phases.

If the name of the field changes or is removed, then every downstream driver

will break. On the other hand, if only the bus layer (and not the device

layer) accesses struct device, it is only that layer that needs to change.

The above abstraction prevents unnecessary pain during transitional phases.

If it were not done this way, then when a field was renamed or removed, every

downstream driver would break.  On the other hand, if only the bus layer

(and not the device layer) accesses the struct device, it is only the bus

layer that needs to change.

User Interface

By virtue of having a complete hierarchical view of all the devices in the

system, exporting a complete hierarchical view to userspace becomes relatively

easy. This has been accomplished by implementing a special purpose virtual

file system named sysfs. It is hence possible for the user to mount the

whole sysfs filesystem anywhere in userspace.

file system named sysfs.

Almost all mainstream Linux distros mount this filesystem automatically; you

can see some variation of the following in the output of the "mount" command:

$ mount

...

none on /sys type sysfs (rw,noexec,nosuid,nodev)

...

$

This can be done permanently by providing the following entry into the

/etc/fstab (under the provision that the mount point does exist, of course):

The auto-mounting of sysfs is typically accomplished by an entry similar to

the following in the /etc/fstab file:

none     	/sys	sysfs    defaults	  	0 0

Or by hand on the command line:

or something similar in the /lib/init/fstab file on Debian-based systems:

none            /sys    sysfs    nodev,noexec,nosuid    0 0

If sysfs is not automatically mounted, you can always do it manually with:

# mount -t sysfs sysfs /sys

				      struct dentry *parent, u16 *value);

    struct dentry *debugfs_create_x32(const char *name, mode_t mode,

				      struct dentry *parent, u32 *value);

Note that there is no debugfs_create_x64().

    struct dentry *debugfs_create_x64(const char *name, mode_t mode,

				      struct dentry *parent, u64 *value);

These functions are useful as long as the developer knows the size of the

value to be exported.  Some types can have different widths on different

锘?Chinese translated version of Documentation/email-clients.txt

Chinese translated version of Documentation/email-clients.txt

If you have any comment or update to the content, please contact the

original document maintainer directly.  However, if you have a problem

Chinese maintainer: Harry Wei <harryxiyou@gmail.com>

---------------------------------------------------------------------

Documentation/email-clients.txt ???涓????缈昏??

Documentation/email-clients.txt 的中文翻译

濡??????宠??璁烘????存?版???????????瀹癸??璇风?存?ヨ??绯诲?????妗ｇ??缁存?よ?????濡????浣?浣跨?ㄨ?辨??

浜ゆ???????伴?剧??璇?锛?涔????浠ュ??涓???????缁存?よ??姹???┿??濡???????缈昏????存?颁???????舵?????缈?

璇?瀛???ㄩ??棰?锛?璇疯??绯讳腑??????缁存?よ?????

如果想评论或更新本文的内容，请直接联系原文档的维护者。如果你使用英文

交流有困难的话，也可以向中文版维护者求助。如果本翻译更新不及时或者翻

译存在问题，请联系中文版维护者。

涓???????缁存?よ??锛? 璐惧??濞?  Harry Wei <harryxiyou@gmail.com>

涓???????缈昏?????锛? 璐惧??濞?  Harry Wei <harryxiyou@gmail.com>

涓?????????¤?????锛? Yinglin Luan <synmyth@gmail.com>

中文版维护者： 贾威威  Harry Wei <harryxiyou@gmail.com>

中文版翻译者： 贾威威  Harry Wei <harryxiyou@gmail.com>

中文版校译者： Yinglin Luan <synmyth@gmail.com>

		Xiaochen Wang <wangxiaochen0@gmail.com>

		yaxinsn <yaxinsn@163.com>

浠ヤ??涓烘?ｆ??

以下为正文

---------------------------------------------------------------------

Linux???浠跺?㈡?风?????缃?淇℃??

Linux邮件客户端配置信息

======================================================================

?????????缃?

普通配置

----------------------------------------------------------------------

Linux?????歌ˉ涓???????杩????浠惰?????浜ょ??锛????濂芥??琛ヤ??浣?涓洪??浠朵????????宓?????????????浜?缁存?よ??

??ユ?堕??浠讹??浣???????浠剁?????瀹规?煎??搴?璇ユ??"text/plain"?????惰??锛????浠朵????????涓?璧???????锛?

???涓鸿??浼?浣胯ˉ涓????寮???ㄩ?ㄥ????ㄨ??璁鸿??绋?涓???????寰???伴?俱??

Linux内核补丁是通过邮件被提交的，最好把补丁作为邮件体的内嵌文本。有些维护者

接收附件，但是附件的内容格式应该是"text/plain"。然而，附件一般是不赞成的，

因为这会使补丁的引用部分在评论过程中变的很困难。

??ㄦ?ュ?????Linux?????歌ˉ涓???????浠跺?㈡?风????ㄥ?????琛ヤ????跺??璇ュ??浜?????????????濮???舵?????渚?濡?锛?

浠?浠?涓???芥?瑰?????????????ゅ?惰〃绗???????绌烘?硷???????虫????ㄦ??涓?琛????寮?澶存?????缁?灏俱??

用来发送Linux内核补丁的邮件客户端在发送补丁时应该处于文本的原始状态。例如，

他们不能改变或者删除制表符或者空格，甚至是在每一行的开头或者结尾。

涓?瑕????杩?"format=flowed"妯″????????琛ヤ?????杩???蜂??寮?璧蜂?????棰????浠ュ?????瀹崇?????琛????

不要通过"format=flowed"模式发送补丁。这样会引起不可预期以及有害的断行。

涓?瑕?璁╀????????浠跺?㈡?风??杩?琛??????ㄦ?㈣?????杩???蜂??浼???村??浣????琛ヤ?????

不要让你的邮件客户端进行自动换行。这样也会破坏你的补丁。

???浠跺?㈡?风??涓???芥?瑰???????????瀛?绗????缂??????瑰?????瑕??????????琛ヤ???????芥??ASCII??????UTF-8缂??????瑰??锛?

濡????浣?浣跨??UTF-8缂??????瑰???????????浠讹????ｄ??浣?灏?浼???垮??涓?浜??????藉????????瀛?绗???????棰????

邮件客户端不能改变文本的字符集编码方式。要发送的补丁只能是ASCII或者UTF-8编码方式，

如果你使用UTF-8编码方式发送邮件，那么你将会避免一些可能发生的字符集问题。

???浠跺?㈡?风??搴?璇ュ舰???骞朵??淇???? References: ?????? In-Reply-To: ???棰?锛???ｄ??

???浠惰??棰?灏变??浼?涓???????

邮件客户端应该形成并且保持 References: 或者 In-Reply-To: 标题，那么

邮件话题就不会中断。

澶???剁??甯?(?????????璐寸??甯?)???甯镐????界?ㄤ??琛ヤ??锛????涓哄?惰〃绗?浼?杞????涓虹┖??笺??浣跨??xclipboard, xclip

??????xcutsel涔?璁稿??浠ワ??浣???????濂芥??璇?涓?涓?????????垮??浣跨?ㄥ????剁??甯????

复制粘帖(或者剪贴粘帖)通常不能用于补丁，因为制表符会转换为空格。使用xclipboard, xclip

或者xcutsel也许可以，但是最好测试一下或者避免使用复制粘帖。

涓?瑕???ㄤ娇???PGP/GPG缃插????????浠朵腑??????琛ヤ?????杩???蜂??浣垮??寰?澶???????涓???借?诲??????????ㄤ??浣????琛ヤ?????

锛?杩?涓????棰?搴?璇ユ?????浠ヤ慨澶????锛?

不要在使用PGP/GPG署名的邮件中包含补丁。这样会使得很多脚本不能读取和适用于你的补丁。

（这个问题应该是可以修复的）

??ㄧ???????搁??浠跺??琛ㄥ?????琛ヤ??涔????锛?缁????宸卞?????涓?涓?琛ヤ?????涓?涓???????涓绘??锛?淇?瀛???ユ?跺?扮??

???浠讹??灏?琛ヤ?????'patch'??戒护???涓?锛?濡??????????浜?锛????缁??????搁??浠跺??琛ㄥ????????

在给内核邮件列表发送补丁之前，给自己发送一个补丁是个不错的主意，保存接收到的

邮件，将补丁用'patch'命令打上，如果成功了，再给内核邮件列表发送。

涓?浜????浠跺?㈡?风?????绀?

一些邮件客户端提示

----------------------------------------------------------------------

杩????缁???轰??浜?璇?缁????MUA???缃????绀猴?????浠ョ?ㄤ??缁?Linux?????稿?????琛ヤ?????杩?浜?骞朵???????虫??

?????????杞?浠跺?????缃???荤?????

这里给出一些详细的MUA配置提示，可以用于给Linux内核发送补丁。这些并不意味是

所有的软件包配置总结。

璇存??锛?

TUI = 浠ユ?????涓哄?虹???????ㄦ?锋?ュ??

GUI = ??惧舰?????㈢?ㄦ?锋?ュ??

说明：

TUI = 以文本为基础的用户接口

GUI = 图形界面用户接口

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Alpine (TUI)

???缃????椤癸??

???"Sending Preferences"??ㄥ??锛?

配置选项：

在"Sending Preferences"部分：

- "Do Not Send Flowed Text"蹇?椤诲?????

- "Strip Whitespace Before Sending"蹇?椤诲?抽??

- "Do Not Send Flowed Text"必须开启

- "Strip Whitespace Before Sending"必须关闭

褰???????浠舵?讹????????搴?璇ユ?惧?ㄨˉ涓?浼???虹?扮????版?癸????跺?????涓?CTRL-R缁???????锛?浣挎??瀹????

琛ヤ?????浠跺????ュ?伴??浠朵腑???

当写邮件时，光标应该放在补丁会出现的地方，然后按下CTRL-R组合键，使指定的

补丁文件嵌入到邮件中。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Evolution (GUI)

涓?浜?寮????????????????浣跨?ㄥ????????琛ヤ??

一些开发者成功的使用它发送补丁

褰??????╅??浠堕??椤癸??Preformat

  浠?Format->Heading->Preformatted (Ctrl-7)??????宸ュ?锋??

当选择邮件选项：Preformat

  从Format->Heading->Preformatted (Ctrl-7)或者工具栏

??跺??浣跨??锛?

  Insert->Text File... (Alt-n x)?????ヨˉ涓????浠躲??

然后使用：

  Insert->Text File... (Alt-n x)插入补丁文件。

浣?杩????浠?"diff -Nru old.c new.c | xclip"锛???????Preformat锛???跺??浣跨?ㄤ腑??撮??杩?琛?绮?甯????

你还可以"diff -Nru old.c new.c | xclip"，选择Preformat，然后使用中间键进行粘帖。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Kmail (GUI)

涓?浜?寮????????????????浣跨?ㄥ????????琛ヤ?????

一些开发者成功的使用它发送补丁。

榛?璁よ?剧疆涓?涓?HTML??煎??????????????锛?涓?瑕??????ㄥ?????

默认设置不为HTML格式是合适的；不要启用它。

褰?涔????涓?灏????浠剁????跺??锛???ㄩ??椤逛?????涓?瑕??????╄????ㄦ?㈣????????涓????缂虹?瑰氨???浣???ㄩ??浠朵腑杈???ョ??浠讳????????

??戒??浼?琚??????ㄦ?㈣??锛????姝や??蹇?椤诲?ㄥ?????琛ヤ??涔?????????ㄦ?㈣????????绠?????????规??灏辨???????ㄨ????ㄦ?㈣????ヤ功??????浠讹??

??跺?????瀹?淇?瀛?涓鸿??绋裤??涓????浣???ㄨ??绋夸腑???娆℃??寮?瀹?锛?瀹?宸茬????ㄩ?ㄨ????ㄦ?㈣??浜?锛???ｄ??浣???????浠惰?界?舵病???

?????╄????ㄦ?㈣??锛?浣????杩?涓?浼?澶卞?诲凡???????????ㄦ?㈣?????

当书写一封邮件的时候，在选项下面不要选择自动换行。唯一的缺点就是你在邮件中输入的任何文本

都不会被自动换行，因此你必须在发送补丁之前手动换行。最简单的方法就是启用自动换行来书写邮件，

然后把它保存为草稿。一旦你在草稿中再次打开它，它已经全部自动换行了，那么你的邮件虽然没有

选择自动换行，但是还不会失去已有的自动换行。

??ㄩ??浠剁??搴????锛??????ヨˉ涓?涔????锛???句??甯哥?ㄧ??琛ヤ??瀹????绗?锛?涓?涓?杩?瀛????(---)???

在邮件的底部，插入补丁之前，放上常用的补丁定界符：三个连字号(---)。

??跺?????"Message"????????＄??锛??????╂????ユ??浠讹????ョ????????浣????琛ヤ?????浠躲??杩????涓?涓?棰?澶???????椤癸??浣????浠?

???杩?瀹????缃?浣???????浠跺缓绔?宸ュ?锋????????锛?杩????浠ュ甫涓?"insert file"??炬?????

然后在"Message"菜单条目，选择插入文件，接着选取你的补丁文件。还有一个额外的选项，你可以

通过它配置你的邮件建立工具栏菜单，还可以带上"insert file"图标。

浣????浠ュ????ㄥ?伴??杩?GPG???璁伴??浠讹??浣???????宓?琛ヤ?????濂戒??瑕?浣跨??GPG???璁板??浠????浣?涓哄??宓??????????绛惧??琛ヤ??锛?

褰?浠?GPG涓???????7浣?缂??????朵??浣夸??浠?????????村??澶???????

你可以安全地通过GPG标记附件，但是内嵌补丁最好不要使用GPG标记它们。作为内嵌文本的签发补丁，

当从GPG中提取7位编码时会使他们变的更加复杂。

濡????浣????瑕?浠ラ??浠剁??褰㈠????????琛ヤ??锛???ｄ??灏卞?抽????瑰?婚??浠讹????跺?????涓?灞???э??绐????"Suggest automatic

display"锛?杩???峰??宓????浠舵?村?规??璁╄?昏???????般??

如果你非要以附件的形式发送补丁，那么就右键点击附件，然后选中属性，突出"Suggest automatic

display"，这样内嵌附件更容易让读者看到。

褰?浣?瑕?淇?瀛?灏?瑕?????????????宓???????琛ヤ??锛?浣????浠ヤ??娑???????琛ㄧ????奸????╁?????琛ヤ????????浠讹????跺????冲?婚?????

"save as"???浣????浠ヤ娇??ㄤ??涓?娌℃????存?圭????????琛ヤ????????浠讹??濡????瀹????浠ユ?ｇ‘???褰㈠??缁???????褰?浣?姝ｇ????ㄥ??

???宸辩??绐???ｄ??涓?瀵????锛???ｆ?舵病??????椤瑰??浠ヤ??瀛????浠?--宸茬?????涓?涓?杩???风??bug琚?姹???ュ?颁??kmail???bugzilla

骞朵??甯????杩?灏?浼?琚?澶??????????浠舵??浠ュ?????瀵规??涓???ㄦ?峰??璇诲???????????琚?淇?瀛????锛????浠ュ?????浣???虫?????浠跺????跺?板?朵????版?癸??

浣?涓?寰?涓????浠?浠????????????逛负缁?????????翠?????璇汇??

当你要保存将要发送的内嵌文本补丁，你可以从消息列表窗格选择包含补丁的邮件，然后右击选择

"save as"。你可以使用一个没有更改的包含补丁的邮件，如果它是以正确的形式组成。当你正真在它

自己的窗口之下察看，那时没有选项可以保存邮件--已经有一个这样的bug被汇报到了kmail的bugzilla

并且希望这将会被处理。邮件是以只针对某个用户可读写的权限被保存的，所以如果你想把邮件复制到其他地方，

你不得不把他们的权限改为组或者整体可读。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Lotus Notes (GUI)

涓?瑕?浣跨?ㄥ?????

不要使用它。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Mutt (TUI)

寰?澶?Linux寮????浜哄??浣跨??mutt瀹㈡?风??锛????浠ヨ?????瀹????瀹?宸ヤ????????甯告??浜????

很多Linux开发人员使用mutt客户端，所以证明它肯定工作的非常漂亮。

Mutt涓????甯?缂?杈????锛????浠ヤ??绠′??浣跨?ㄤ??涔?缂?杈???ㄩ?戒??搴?璇ュ甫????????ㄦ??琛????澶у????扮??杈???ㄩ?藉甫???

涓?涓?"insert file"???椤癸??瀹????浠ラ??杩?涓???瑰?????浠跺??瀹圭????瑰???????ユ??浠躲??

Mutt不自带编辑器，所以不管你使用什么编辑器都不应该带有自动断行。大多数编辑器都带有

一个"insert file"选项，它可以通过不改变文件内容的方式插入文件。

'vim'浣?涓?mutt???缂?杈????锛?

'vim'作为mutt的编辑器：

  set editor="vi"

  濡????浣跨??xclip锛???插?ヤ互涓???戒护

  如果使用xclip，敲入以下命令

  :set paste

  ???涓????涔??????????shift-insert??????浣跨??

  按中键之前或者shift-insert或者使用

  :r filename

濡??????宠?????琛ヤ??浣?涓哄??宓??????????

(a)ttach宸ヤ?????寰?濂斤??涓?甯????"set paste"???

如果想要把补丁作为内嵌文本。

(a)ttach工作的很好，不带有"set paste"。

???缃????椤癸??

瀹?搴?璇ヤ互榛?璁よ?剧疆???褰㈠??宸ヤ?????

??惰??锛????"send_charset"璁剧疆涓?"us-ascii::utf-8"涔????涓?涓?涓???????涓绘?????

配置选项：

它应该以默认设置的形式工作。

然而，把"send_charset"设置为"us-ascii::utf-8"也是一个不错的主意。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Pine (TUI)

Pine杩???绘??涓?浜?绌烘?煎????????棰?锛?浣????杩?浜???板?ㄥ??璇ラ?借??淇?澶?浜????

Pine过去有一些空格删减问题，但是这些现在应该都被修复了。

濡???????浠ワ??璇蜂娇???alpine(pine???缁ф?胯??)

如果可以，请使用alpine(pine的继承者)

???缃????椤癸??

- ???杩?????????????瑕?娑???ゆ??绋???????

- "no-strip-whitespace-before-send"???椤逛????????瑕???????

配置选项：

- 最近的版本需要消除流程文本

- "no-strip-whitespace-before-send"选项也是需要的。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sylpheed (GUI)

- ???宓??????????浠ュ??濂界??宸ヤ??锛???????浣跨?ㄩ??浠讹?????

- ???璁镐娇??ㄥ????ㄧ??缂?杈???ㄣ??

- 瀵逛?????褰?杈?澶???堕??甯告?????

- 濡???????杩?non-SSL杩???ワ?????娉?浣跨??TLS SMTP?????????

- ??ㄧ?????绐???ｄ腑???涓?涓?寰??????ㄧ??ruler bar???

- 缁???板?????涓?娣诲????板??灏变??浼?姝ｇ‘???浜?瑙ｆ?剧ず??????

- 内嵌文本可以很好的工作（或者使用附件）。

- 允许使用外部的编辑器。

- 对于目录较多时非常慢。

- 如果通过non-SSL连接，无法使用TLS SMTP授权。

- 在组成窗口中有一个很有用的ruler bar。

- 给地址本中添加地址就不会正确的了解显示名。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thunderbird (GUI)

榛?璁ゆ????典??锛?thunderbird寰?瀹规??????????????锛?浣????杩????涓?浜???规?????浠ュ己??跺?????寰???村ソ???

默认情况下，thunderbird很容易损坏文本，但是还有一些方法可以强制它变得更好。

- ??ㄧ?ㄦ?峰????疯?剧疆???锛?缁???????瀵诲??锛?涓?瑕???????"Compose messages in HTML format"???

- 在用户帐号设置里，组成和寻址，不要选择"Compose messages in HTML format"。

- 缂?杈?浣????Thunderbird???缃?璁剧疆??ヤ娇瀹?涓?瑕????琛?浣跨??锛?user_pref("mailnews.wraplength", 0);

- 编辑你的Thunderbird配置设置来使它不要拆行使用：user_pref("mailnews.wraplength", 0);

- 缂?杈?浣????Thunderbird???缃?璁剧疆锛?浣垮??涓?瑕?浣跨??"format=flowed"??煎??锛?user_pref("mailnews.

- 编辑你的Thunderbird配置设置，使它不要使用"format=flowed"格式：user_pref("mailnews.

  send_plaintext_flowed", false);

- 浣????瑕?浣?Thunderbird???涓洪???????煎????瑰??锛?

  濡????榛?璁ゆ????典??浣?涔??????????HTML??煎??锛???ｄ?????寰???俱??浠?浠?浠????棰???????涓????妗?涓???????"Preformat"??煎?????

  濡????榛?璁ゆ????典??浣?涔??????????????????煎??锛?浣?涓?寰????瀹???逛负HTML??煎??锛?浠?浠?浣?涓轰??娆℃?х??锛???ヤ功?????扮??娑????锛?

  ??跺??寮哄?朵娇瀹??????版???????煎??锛???????瀹?灏变?????琛????瑕?瀹???板??锛???ㄥ??淇＄????炬??涓?浣跨??shift?????ヤ娇瀹????涓?HTML

  ??煎??锛???跺?????棰???????涓????妗?涓???????"Preformat"??煎?????

- 你需要使Thunderbird变为预先格式方式：

  如果默认情况下你书写的是HTML格式，那不是很难。仅仅从标题栏的下拉框中选择"Preformat"格式。

  如果默认情况下你书写的是文本格式，你不得把它改为HTML格式（仅仅作为一次性的）来书写新的消息，

  然后强制使它回到文本格式，否则它就会拆行。要实现它，在写信的图标上使用shift键来使它变为HTML

  格式，然后标题栏的下拉框中选择"Preformat"格式。

- ???璁镐娇??ㄥ????ㄧ??缂?杈????锛?

  ???瀵?Thunderbird???琛ヤ?????绠?????????规??灏辨??浣跨?ㄤ??涓?"external editor"??╁??锛???跺??浣跨?ㄤ????????娆㈢??

  $EDITOR??ヨ?诲???????????骞惰ˉ涓???版?????涓????瑕?瀹???板??锛????浠ヤ??杞藉苟涓?瀹?瑁?杩?涓???╁??锛???跺??娣诲??涓?涓?浣跨?ㄥ?????

  ??????View->Toolbars->Customize...??????褰?浣?涔????淇℃???????跺??浠?浠???瑰?诲??灏卞??浠ヤ?????

- 允许使用外部的编辑器：

  针对Thunderbird打补丁最简单的方法就是使用一个"external editor"扩展，然后使用你最喜欢的

  $EDITOR来读取或者合并补丁到文本中。要实现它，可以下载并且安装这个扩展，然后添加一个使用它的

  按键View->Toolbars->Customize...最后当你书写信息的时候仅仅点击它就可以了。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

TkRat (GUI)

???浠ヤ娇??ㄥ?????浣跨??"Insert file..."??????澶???ㄧ??缂?杈???ㄣ??

可以使用它。使用"Insert file..."或者外部的编辑器。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Gmail (Web GUI)

涓?瑕?浣跨?ㄥ????????琛ヤ?????

不要使用它发送补丁。

Gmail缃?椤靛?㈡?风???????ㄥ?版????惰〃绗?杞????涓虹┖??笺??

Gmail网页客户端自动地把制表符转换为空格。

??界?跺?惰〃绗?杞????涓虹┖??奸??棰????浠ヨ??澶???ㄧ??杈???ㄨВ??筹???????跺??杩?浼?浣跨?ㄥ??杞???㈣?????姣?琛???????涓?78涓?瀛?绗????

虽然制表符转换为空格问题可以被外部编辑器解决，同时它还会使用回车换行把每行拆分为78个字符。

???涓?涓????棰????Gmail杩?浼????浠讳??涓????ASCII???瀛?绗????淇℃????逛负base64缂???????瀹????涓?瑗垮????????娆ф床浜虹?????瀛????

另一个问题是Gmail还会把任何不是ASCII的字符的信息改为base64编码。它把东西变的像欧洲人的名字。

                                ###