Re: [PATCH] Documentation: email-clients.txt

[Austin S Hemmelgarn]

On 2015-12-06 15:52, Randy Dunlap wrote:

On 12/06/15 07:30, Jonathan Corbet wrote:

On Sun, 6 Dec 2015 01:09:39 -0500
Sanidhya Solanki  wrote:


Patch included below. As an aside, thank you for the excellent work on
the books and other documentation.


Thanks for the nice comments.  Future praise, however, should go below the
"---" marker so I don't have to edit it out of the changelogs :)


Documentation: email-clients.txt

The information for Claws Mail, Evolution and Thunderbird was out of
date. It has been updated with new instructions and warnings.


So I feel like I'm missing some sort of intentional irony, but I do have
to point out that this patch has been corrupted by your mailer and cannot
be applied.  The usual advice here applies: try sending the email to
yourself and applying the result.


diff --git a/Documentation/email-clients.txt
b/Documentation/email-clients.txt index 2d485de..8819c90 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -79,17 +79,27 @@ to insert into the message.
  ~~
  Claws Mail (GUI)

-Works. Some people use this successfully for patches.
+Tested and Works as of December 2015. Some people use this successfully
+for patches.


Not sure we need datestamps like this here.  In any case, a few kernel
developers are known to use claws - myself included.  We test it every day :)


  To insert a patch use Message->Insert File (CTRL+i) or an external
editor.
  If the inserted patch has to be edited in the Claws composition window
  "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
should be -disabled.
+disabled. Also, under the heading "View", sub-heading "Character
Encoding" +, choose "Unicode (UTF - 8)"
+
+Do remember that if you insert or type something in the main text area,
+and decide to delete it, you will need to reset the formatting by
opening +a new window for the change you want to make. Re-using the
window in which +you deleted the text will lead to the new message
being mangled.


...and this makes no sense to me.  I've never seen any such behavior in
claws?


  Evolution (GUI)

+As of December 2015, the composing & inserting  method described below
+does not work.


Could it really be that nobody is using evolution?  Much nicer here would
be to describe how it fails to work, and, ideally, come up with a fix.


  Some people use this successfully for patches.

  When composing mail select: Preformat
@@ -244,8 +254,9 @@ Sylpheed (GUI)
  ~~
  Thunderbird (GUI)

-Thunderbird is an Outlook clone that likes to mangle text, but there
are ways -to coerce it into behaving.
+Thunderbird is an Outlook clone that likes to mangle text, but there
are +ways to coerce it into behaving. In December 2015, the internal
editor +options do not appear to work.


Again, what's the problem here?  I suspect there are people using
Thunderbird out there, how are they doing it if the documented approach
doesn't work?


I use thunderbird with an external editor plugin, so I just insert patches with
the external editor.

It may be worth noting that you can get a plugin that lets you just 
toggle word-wrap with the internal editor (rather un-inventively called 
'Toggle Word Wrap'), and that _seems_ to work most of the time.  The 
down side to this of course is that it toggles for the whole message, 
and not just parts of it.





smime.p7s
Description: S/MIME Cryptographic Signature

Re: [PATCH] Documentation: email-clients.txt

[Clemens Ladisch]

Sanidhya Solanki wrote:
>  Claws Mail (GUI)
>
> -Works. Some people use this successfully for patches.
> +Tested and Works as of December 2015. Some people use this successfully
> +for patches.

"Some people" still doesn't include you:

> -Thunderbird is an Outlook clone that likes to mangle text, but there
> are ways -to coerce it into behaving.
> +Thunderbird is an Outlook clone that likes to mangle text, but there
> are +ways to coerce it into behaving. In December 2015, the internal
> editor +options do not appear to work.

How exactly?  Thunderbird appears to work for me, and doesn't break long lines 
or sends plain text as "flowed".

And version numbers might be more useful than dates.


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Clemens Ladisch]

Sanidhya Solanki wrote:
>  Claws Mail (GUI)
>
> -Works. Some people use this successfully for patches.
> +Tested and Works as of December 2015. Some people use this successfully
> +for patches.

"Some people" still doesn't include you:

> -Thunderbird is an Outlook clone that likes to mangle text, but there
> are ways -to coerce it into behaving.
> +Thunderbird is an Outlook clone that likes to mangle text, but there
> are +ways to coerce it into behaving. In December 2015, the internal
> editor +options do not appear to work.

How exactly?  Thunderbird appears to work for me, and doesn't break long lines 
or sends plain text as "flowed".

And version numbers might be more useful than dates.


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Austin S Hemmelgarn]

On 2015-12-06 15:52, Randy Dunlap wrote:

On 12/06/15 07:30, Jonathan Corbet wrote:

On Sun, 6 Dec 2015 01:09:39 -0500
Sanidhya Solanki  wrote:


Patch included below. As an aside, thank you for the excellent work on
the books and other documentation.


Thanks for the nice comments.  Future praise, however, should go below the
"---" marker so I don't have to edit it out of the changelogs :)


Documentation: email-clients.txt

The information for Claws Mail, Evolution and Thunderbird was out of
date. It has been updated with new instructions and warnings.


So I feel like I'm missing some sort of intentional irony, but I do have
to point out that this patch has been corrupted by your mailer and cannot
be applied.  The usual advice here applies: try sending the email to
yourself and applying the result.


diff --git a/Documentation/email-clients.txt
b/Documentation/email-clients.txt index 2d485de..8819c90 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -79,17 +79,27 @@ to insert into the message.
  ~~
  Claws Mail (GUI)

-Works. Some people use this successfully for patches.
+Tested and Works as of December 2015. Some people use this successfully
+for patches.


Not sure we need datestamps like this here.  In any case, a few kernel
developers are known to use claws - myself included.  We test it every day :)


  To insert a patch use Message->Insert File (CTRL+i) or an external
editor.
  If the inserted patch has to be edited in the Claws composition window
  "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
should be -disabled.
+disabled. Also, under the heading "View", sub-heading "Character
Encoding" +, choose "Unicode (UTF - 8)"
+
+Do remember that if you insert or type something in the main text area,
+and decide to delete it, you will need to reset the formatting by
opening +a new window for the change you want to make. Re-using the
window in which +you deleted the text will lead to the new message
being mangled.


...and this makes no sense to me.  I've never seen any such behavior in
claws?


  Evolution (GUI)

+As of December 2015, the composing & inserting  method described below
+does not work.


Could it really be that nobody is using evolution?  Much nicer here would
be to describe how it fails to work, and, ideally, come up with a fix.


  Some people use this successfully for patches.

  When composing mail select: Preformat
@@ -244,8 +254,9 @@ Sylpheed (GUI)
  ~~
  Thunderbird (GUI)

-Thunderbird is an Outlook clone that likes to mangle text, but there
are ways -to coerce it into behaving.
+Thunderbird is an Outlook clone that likes to mangle text, but there
are +ways to coerce it into behaving. In December 2015, the internal
editor +options do not appear to work.


Again, what's the problem here?  I suspect there are people using
Thunderbird out there, how are they doing it if the documented approach
doesn't work?


I use thunderbird with an external editor plugin, so I just insert patches with
the external editor.

It may be worth noting that you can get a plugin that lets you just 
toggle word-wrap with the internal editor (rather un-inventively called 
'Toggle Word Wrap'), and that _seems_ to work most of the time.  The 
down side to this of course is that it toggles for the whole message, 
and not just parts of it.





smime.p7s
Description: S/MIME Cryptographic Signature

Re: [PATCH] Documentation: email-clients.txt

[Randy Dunlap]

On 12/06/15 20:13, Joe Perches wrote:
> On Sun, 2015-12-06 at 19:10 -0500, Sanidhya Solanki wrote:
>> Try the patch I just send you.
> 
> I think you should first try the patch you just sent yourself.
> 

Yes, it appears to be mangled. :(


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Joe Perches]

On Sun, 2015-12-06 at 19:10 -0500, Sanidhya Solanki wrote:
> Try the patch I just send you.

I think you should first try the patch you just sent yourself.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Sanidhya Solanki]

So, now that everyone has sounded off about their clients, I guess we
can know how people still use the clients that are included in the
documentation.

As a side note, JC, I think I have figured out why the patch did not
apply for you but works for me. It appears, ostensibly, that when
using CLaws 3.12 on Fedora, I can send patches that seem to work only
after inserting the file. If I add anything in the compose window after
inserting the patch, the client appears to mangle it. That would
explain the issues you experienced and  I still seem to be having. 

As an aside, I do send every patch to myself on multiple accounts using
Claws, then compare the SHA512 hash, and as a final measure reset git
and reapply the patch. Only then do I send it to the mailing list.

If no one else provides a patch including the information supplied by
this email chain in 5 days, then I will collect it all and send it to
you in a patch.

Best give people a few days to claim their findings as their own,
without delaying it too much.

Try the patch I just send you.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Sanidhya Solanki]

[PATCH] Documentation: email-clients.txt

The information for Claws Mail, Evolution and Thunderbird was out of
date. It has been updated with new instructions and warnings.

Signed-off-by: Sanidhya Solanki 
---
 Documentation/email-clients.txt | 19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/Documentation/email-clients.txt
b/Documentation/email-clients.txt index 2d485de..8819c90 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -79,17 +79,27 @@ to insert into the message.
 ~~
 Claws Mail (GUI)
 
-Works. Some people use this successfully for patches.
+Tested and Works as of December 2015. Some people use this successfully
+for patches.
 
 To insert a patch use Message->Insert File (CTRL+i) or an external
editor. 
 If the inserted patch has to be edited in the Claws composition window
 "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
should be -disabled.
+disabled. Also, under the heading "View", sub-heading "Character
Encoding" +, choose "Unicode (UTF - 8)"
+
+Do remember that if you insert or type something in the main text area,
+and decide to delete it, you will need to reset the formatting by
opening +a new window for the change you want to make. Re-using the
window in which +you deleted the text will lead to the new message
being mangled. 
 ~~
 Evolution (GUI)
 
+As of December 2015, the composing & inserting  method described below
+does not work.
+
 Some people use this successfully for patches.
 
 When composing mail select: Preformat
@@ -244,8 +254,9 @@ Sylpheed (GUI)
 ~~
 Thunderbird (GUI)
 
-Thunderbird is an Outlook clone that likes to mangle text, but there
are ways -to coerce it into behaving.
+Thunderbird is an Outlook clone that likes to mangle text, but there
are +ways to coerce it into behaving. In December 2015, the internal
editor +options do not appear to work.
 
 - Allow use of an external editor:
   The easiest thing to do with Thunderbird and patches is to use an
-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Paul Bolle]

On zo, 2015-12-06 at 22:35 +0100, Paul Bolle wrote:
> That made me shout at my laptop quite a few times already. Oddly
> enough,
> Evolution behaved like it didn't notice that and just kept on doing
> that. What an arrogant application...
> 
> Also note the annoying line breaks in my reply (written with Evolution
> 3.16.5). That nonsense also didn't happen in 3.12.

Being polite with mail, I edited out the lines with these line breaks.
But this self-reply should actually show that annoyance.


Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Paul Bolle]

On zo, 2015-12-06 at 10:11 -0800, Joe Perches wrote:
> The text editor for Evolution versions > 3.12 is broken
> and unrepairable.

My experiences with Evolution 3.16 tell me that might be correct.

> Evolution 3.16 has very poor behavior when replying to
> text emails with tabs.  A ">" character is added before
> every tab in the reply.

That made me shout at my laptop quite a few times already. Oddly enough,
Evolution behaved like it didn't notice that and just kept on doing
that. What an arrogant application...

Also note the annoying line breaks in my reply (written with Evolution
3.16.5). That nonsense also didn't happen in 3.12.

> Evolution 3.18 occasionally uses the Non-Breaking-Space
> (NBSP) character instead of the standand ASCII 32 space
> which breaks applying patches sent with that email client.

(I've only been using Evolution for a decade now. But still the thought
that I really should be looking into a new client scares me quite a
bit.)


Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Randy Dunlap]

On 12/06/15 07:30, Jonathan Corbet wrote:
> On Sun, 6 Dec 2015 01:09:39 -0500
> Sanidhya Solanki  wrote:
> 
>> Patch included below. As an aside, thank you for the excellent work on
>> the books and other documentation.
> 
> Thanks for the nice comments.  Future praise, however, should go below the
> "---" marker so I don't have to edit it out of the changelogs :)
> 
>> Documentation: email-clients.txt
>>
>> The information for Claws Mail, Evolution and Thunderbird was out of
>> date. It has been updated with new instructions and warnings.
> 
> So I feel like I'm missing some sort of intentional irony, but I do have
> to point out that this patch has been corrupted by your mailer and cannot
> be applied.  The usual advice here applies: try sending the email to
> yourself and applying the result.
> 
>> diff --git a/Documentation/email-clients.txt
>> b/Documentation/email-clients.txt index 2d485de..8819c90 100644
>> --- a/Documentation/email-clients.txt
>> +++ b/Documentation/email-clients.txt
>> @@ -79,17 +79,27 @@ to insert into the message.
>>  ~~
>>  Claws Mail (GUI)
>>  
>> -Works. Some people use this successfully for patches.
>> +Tested and Works as of December 2015. Some people use this successfully
>> +for patches.
> 
> Not sure we need datestamps like this here.  In any case, a few kernel
> developers are known to use claws - myself included.  We test it every day :)
> 
>>  To insert a patch use Message->Insert File (CTRL+i) or an external
>> editor. 
>>  If the inserted patch has to be edited in the Claws composition window
>>  "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
>> should be -disabled.
>> +disabled. Also, under the heading "View", sub-heading "Character
>> Encoding" +, choose "Unicode (UTF - 8)"
>> +
>> +Do remember that if you insert or type something in the main text area,
>> +and decide to delete it, you will need to reset the formatting by
>> opening +a new window for the change you want to make. Re-using the
>> window in which +you deleted the text will lead to the new message
>> being mangled. 
> 
> ...and this makes no sense to me.  I've never seen any such behavior in
> claws?
> 
>>  Evolution (GUI)
>>  
>> +As of December 2015, the composing & inserting  method described below
>> +does not work.
> 
> Could it really be that nobody is using evolution?  Much nicer here would
> be to describe how it fails to work, and, ideally, come up with a fix.
> 
>>  Some people use this successfully for patches.
>>  
>>  When composing mail select: Preformat
>> @@ -244,8 +254,9 @@ Sylpheed (GUI)
>>  ~~
>>  Thunderbird (GUI)
>>  
>> -Thunderbird is an Outlook clone that likes to mangle text, but there
>> are ways -to coerce it into behaving.
>> +Thunderbird is an Outlook clone that likes to mangle text, but there
>> are +ways to coerce it into behaving. In December 2015, the internal
>> editor +options do not appear to work.
> 
> Again, what's the problem here?  I suspect there are people using
> Thunderbird out there, how are they doing it if the documented approach
> doesn't work?

I use thunderbird with an external editor plugin, so I just insert patches with
the external editor.


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Jonathan Corbet]

On Sun, 06 Dec 2015 10:11:04 -0800
Joe Perches  wrote:

> > Could it really be that nobody is using evolution?  Much nicer here would
> > be to describe how it fails to work, and, ideally, come up with a fix.  
> 
> Evolution 3.12 works fine.
> 
> The text editor for Evolution versions > 3.12 is broken
> and unrepairable.
> 
> Evolution 3.16 has very poor behavior when replying to
> text emails with tabs.  A ">" character is added before
> every tab in the reply.
> 
> Evolution 3.18 occasionally uses the Non-Breaking-Space
> (NBSP) character instead of the standand ASCII 32 space
> which breaks applying patches sent with that email client.

OK, this is good to know; this is the kind of info that should go into
email-clients.txt.

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Joe Perches]

On Sun, 2015-12-06 aASCIIt 08:30 -0700, Jonathan Corbet wrote:
> On Sun, 6 Dec 2015 01:09:39 -0500
> Sanidhya Solanki  wrote:
[]
> >  Evolution (GUI)
> >  
> > +As of December 2015, the composing & inserting  method described below
> > +does not work.
> 
> Could it really be that nobody is using evolution?  Much nicer here would
> be to describe how it fails to work, and, ideally, come up with a fix.

Evolution 3.12 works fine.

The text editor for Evolution versions > 3.12 is broken
and unrepairable.

Evolution 3.16 has very poor behavior when replying to
text emails with tabs.  A ">" character is added before
every tab in the reply.

Evolution 3.18 occasionally uses the Non-Breaking-Space
(NBSP) character instead of the standand ASCII 32 space
which breaks applying patches sent with that email client.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Jonathan Corbet]

On Sun, 6 Dec 2015 01:09:39 -0500
Sanidhya Solanki  wrote:

> Patch included below. As an aside, thank you for the excellent work on
> the books and other documentation.

Thanks for the nice comments.  Future praise, however, should go below the
"---" marker so I don't have to edit it out of the changelogs :)

> Documentation: email-clients.txt
> 
> The information for Claws Mail, Evolution and Thunderbird was out of
> date. It has been updated with new instructions and warnings.

So I feel like I'm missing some sort of intentional irony, but I do have
to point out that this patch has been corrupted by your mailer and cannot
be applied.  The usual advice here applies: try sending the email to
yourself and applying the result.

> diff --git a/Documentation/email-clients.txt
> b/Documentation/email-clients.txt index 2d485de..8819c90 100644
> --- a/Documentation/email-clients.txt
> +++ b/Documentation/email-clients.txt
> @@ -79,17 +79,27 @@ to insert into the message.
>  ~~
>  Claws Mail (GUI)
>  
> -Works. Some people use this successfully for patches.
> +Tested and Works as of December 2015. Some people use this successfully
> +for patches.

Not sure we need datestamps like this here.  In any case, a few kernel
developers are known to use claws - myself included.  We test it every day :)

>  To insert a patch use Message->Insert File (CTRL+i) or an external
> editor. 
>  If the inserted patch has to be edited in the Claws composition window
>  "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
> should be -disabled.
> +disabled. Also, under the heading "View", sub-heading "Character
> Encoding" +, choose "Unicode (UTF - 8)"
> +
> +Do remember that if you insert or type something in the main text area,
> +and decide to delete it, you will need to reset the formatting by
> opening +a new window for the change you want to make. Re-using the
> window in which +you deleted the text will lead to the new message
> being mangled. 

...and this makes no sense to me.  I've never seen any such behavior in
claws?

>  Evolution (GUI)
>  
> +As of December 2015, the composing & inserting  method described below
> +does not work.

Could it really be that nobody is using evolution?  Much nicer here would
be to describe how it fails to work, and, ideally, come up with a fix.

>  Some people use this successfully for patches.
>  
>  When composing mail select: Preformat
> @@ -244,8 +254,9 @@ Sylpheed (GUI)
>  ~~
>  Thunderbird (GUI)
>  
> -Thunderbird is an Outlook clone that likes to mangle text, but there
> are ways -to coerce it into behaving.
> +Thunderbird is an Outlook clone that likes to mangle text, but there
> are +ways to coerce it into behaving. In December 2015, the internal
> editor +options do not appear to work.

Again, what's the problem here?  I suspect there are people using
Thunderbird out there, how are they doing it if the documented approach
doesn't work?

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation: email-clients.txt

[Sanidhya Solanki]

Patch included below. As an aside, thank you for the excellent work on
the books and other documentation.


Documentation: email-clients.txt

The information for Claws Mail, Evolution and Thunderbird was out of
date. It has been updated with new instructions and warnings.

Signed-off-by: Sanidhya Solanki 
---
 Documentation/email-clients.txt | 19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/Documentation/email-clients.txt
b/Documentation/email-clients.txt index 2d485de..8819c90 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -79,17 +79,27 @@ to insert into the message.
 ~~
 Claws Mail (GUI)
 
-Works. Some people use this successfully for patches.
+Tested and Works as of December 2015. Some people use this successfully
+for patches.
 
 To insert a patch use Message->Insert File (CTRL+i) or an external
editor. 
 If the inserted patch has to be edited in the Claws composition window
 "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
should be -disabled.
+disabled. Also, under the heading "View", sub-heading "Character
Encoding" +, choose "Unicode (UTF - 8)"
+
+Do remember that if you insert or type something in the main text area,
+and decide to delete it, you will need to reset the formatting by
opening +a new window for the change you want to make. Re-using the
window in which +you deleted the text will lead to the new message
being mangled. 
 ~~
 Evolution (GUI)
 
+As of December 2015, the composing & inserting  method described below
+does not work.
+
 Some people use this successfully for patches.
 
 When composing mail select: Preformat
@@ -244,8 +254,9 @@ Sylpheed (GUI)
 ~~
 Thunderbird (GUI)
 
-Thunderbird is an Outlook clone that likes to mangle text, but there
are ways -to coerce it into behaving.
+Thunderbird is an Outlook clone that likes to mangle text, but there
are +ways to coerce it into behaving. In December 2015, the internal
editor +options do not appear to work.
 
 - Allow use of an external editor:
   The easiest thing to do with Thunderbird and patches is to use an
-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Jonathan Corbet]

On Sun, 6 Dec 2015 01:09:39 -0500
Sanidhya Solanki  wrote:

> Patch included below. As an aside, thank you for the excellent work on
> the books and other documentation.

Thanks for the nice comments.  Future praise, however, should go below the
"---" marker so I don't have to edit it out of the changelogs :)

> Documentation: email-clients.txt
> 
> The information for Claws Mail, Evolution and Thunderbird was out of
> date. It has been updated with new instructions and warnings.

So I feel like I'm missing some sort of intentional irony, but I do have
to point out that this patch has been corrupted by your mailer and cannot
be applied.  The usual advice here applies: try sending the email to
yourself and applying the result.

> diff --git a/Documentation/email-clients.txt
> b/Documentation/email-clients.txt index 2d485de..8819c90 100644
> --- a/Documentation/email-clients.txt
> +++ b/Documentation/email-clients.txt
> @@ -79,17 +79,27 @@ to insert into the message.
>  ~~
>  Claws Mail (GUI)
>  
> -Works. Some people use this successfully for patches.
> +Tested and Works as of December 2015. Some people use this successfully
> +for patches.

Not sure we need datestamps like this here.  In any case, a few kernel
developers are known to use claws - myself included.  We test it every day :)

>  To insert a patch use Message->Insert File (CTRL+i) or an external
> editor. 
>  If the inserted patch has to be edited in the Claws composition window
>  "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
> should be -disabled.
> +disabled. Also, under the heading "View", sub-heading "Character
> Encoding" +, choose "Unicode (UTF - 8)"
> +
> +Do remember that if you insert or type something in the main text area,
> +and decide to delete it, you will need to reset the formatting by
> opening +a new window for the change you want to make. Re-using the
> window in which +you deleted the text will lead to the new message
> being mangled. 

...and this makes no sense to me.  I've never seen any such behavior in
claws?

>  Evolution (GUI)
>  
> +As of December 2015, the composing & inserting  method described below
> +does not work.

Could it really be that nobody is using evolution?  Much nicer here would
be to describe how it fails to work, and, ideally, come up with a fix.

>  Some people use this successfully for patches.
>  
>  When composing mail select: Preformat
> @@ -244,8 +254,9 @@ Sylpheed (GUI)
>  ~~
>  Thunderbird (GUI)
>  
> -Thunderbird is an Outlook clone that likes to mangle text, but there
> are ways -to coerce it into behaving.
> +Thunderbird is an Outlook clone that likes to mangle text, but there
> are +ways to coerce it into behaving. In December 2015, the internal
> editor +options do not appear to work.

Again, what's the problem here?  I suspect there are people using
Thunderbird out there, how are they doing it if the documented approach
doesn't work?

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Jonathan Corbet]

On Sun, 06 Dec 2015 10:11:04 -0800
Joe Perches  wrote:

> > Could it really be that nobody is using evolution?  Much nicer here would
> > be to describe how it fails to work, and, ideally, come up with a fix.  
> 
> Evolution 3.12 works fine.
> 
> The text editor for Evolution versions > 3.12 is broken
> and unrepairable.
> 
> Evolution 3.16 has very poor behavior when replying to
> text emails with tabs.  A ">" character is added before
> every tab in the reply.
> 
> Evolution 3.18 occasionally uses the Non-Breaking-Space
> (NBSP) character instead of the standand ASCII 32 space
> which breaks applying patches sent with that email client.

OK, this is good to know; this is the kind of info that should go into
email-clients.txt.

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Joe Perches]

On Sun, 2015-12-06 aASCIIt 08:30 -0700, Jonathan Corbet wrote:
> On Sun, 6 Dec 2015 01:09:39 -0500
> Sanidhya Solanki  wrote:
[]
> >  Evolution (GUI)
> >  
> > +As of December 2015, the composing & inserting  method described below
> > +does not work.
> 
> Could it really be that nobody is using evolution?  Much nicer here would
> be to describe how it fails to work, and, ideally, come up with a fix.

Evolution 3.12 works fine.

The text editor for Evolution versions > 3.12 is broken
and unrepairable.

Evolution 3.16 has very poor behavior when replying to
text emails with tabs.  A ">" character is added before
every tab in the reply.

Evolution 3.18 occasionally uses the Non-Breaking-Space
(NBSP) character instead of the standand ASCII 32 space
which breaks applying patches sent with that email client.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation: email-clients.txt

[Sanidhya Solanki]

Patch included below. As an aside, thank you for the excellent work on
the books and other documentation.


Documentation: email-clients.txt

The information for Claws Mail, Evolution and Thunderbird was out of
date. It has been updated with new instructions and warnings.

Signed-off-by: Sanidhya Solanki 
---
 Documentation/email-clients.txt | 19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/Documentation/email-clients.txt
b/Documentation/email-clients.txt index 2d485de..8819c90 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -79,17 +79,27 @@ to insert into the message.
 ~~
 Claws Mail (GUI)
 
-Works. Some people use this successfully for patches.
+Tested and Works as of December 2015. Some people use this successfully
+for patches.
 
 To insert a patch use Message->Insert File (CTRL+i) or an external
editor. 
 If the inserted patch has to be edited in the Claws composition window
 "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
should be -disabled.
+disabled. Also, under the heading "View", sub-heading "Character
Encoding" +, choose "Unicode (UTF - 8)"
+
+Do remember that if you insert or type something in the main text area,
+and decide to delete it, you will need to reset the formatting by
opening +a new window for the change you want to make. Re-using the
window in which +you deleted the text will lead to the new message
being mangled. 
 ~~
 Evolution (GUI)
 
+As of December 2015, the composing & inserting  method described below
+does not work.
+
 Some people use this successfully for patches.
 
 When composing mail select: Preformat
@@ -244,8 +254,9 @@ Sylpheed (GUI)
 ~~
 Thunderbird (GUI)
 
-Thunderbird is an Outlook clone that likes to mangle text, but there
are ways -to coerce it into behaving.
+Thunderbird is an Outlook clone that likes to mangle text, but there
are +ways to coerce it into behaving. In December 2015, the internal
editor +options do not appear to work.
 
 - Allow use of an external editor:
   The easiest thing to do with Thunderbird and patches is to use an
-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Paul Bolle]

On zo, 2015-12-06 at 10:11 -0800, Joe Perches wrote:
> The text editor for Evolution versions > 3.12 is broken
> and unrepairable.

My experiences with Evolution 3.16 tell me that might be correct.

> Evolution 3.16 has very poor behavior when replying to
> text emails with tabs.  A ">" character is added before
> every tab in the reply.

That made me shout at my laptop quite a few times already. Oddly enough,
Evolution behaved like it didn't notice that and just kept on doing
that. What an arrogant application...

Also note the annoying line breaks in my reply (written with Evolution
3.16.5). That nonsense also didn't happen in 3.12.

> Evolution 3.18 occasionally uses the Non-Breaking-Space
> (NBSP) character instead of the standand ASCII 32 space
> which breaks applying patches sent with that email client.

(I've only been using Evolution for a decade now. But still the thought
that I really should be looking into a new client scares me quite a
bit.)


Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Paul Bolle]

On zo, 2015-12-06 at 22:35 +0100, Paul Bolle wrote:
> That made me shout at my laptop quite a few times already. Oddly
> enough,
> Evolution behaved like it didn't notice that and just kept on doing
> that. What an arrogant application...
> 
> Also note the annoying line breaks in my reply (written with Evolution
> 3.16.5). That nonsense also didn't happen in 3.12.

Being polite with mail, I edited out the lines with these line breaks.
But this self-reply should actually show that annoyance.


Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Randy Dunlap]

On 12/06/15 07:30, Jonathan Corbet wrote:
> On Sun, 6 Dec 2015 01:09:39 -0500
> Sanidhya Solanki  wrote:
> 
>> Patch included below. As an aside, thank you for the excellent work on
>> the books and other documentation.
> 
> Thanks for the nice comments.  Future praise, however, should go below the
> "---" marker so I don't have to edit it out of the changelogs :)
> 
>> Documentation: email-clients.txt
>>
>> The information for Claws Mail, Evolution and Thunderbird was out of
>> date. It has been updated with new instructions and warnings.
> 
> So I feel like I'm missing some sort of intentional irony, but I do have
> to point out that this patch has been corrupted by your mailer and cannot
> be applied.  The usual advice here applies: try sending the email to
> yourself and applying the result.
> 
>> diff --git a/Documentation/email-clients.txt
>> b/Documentation/email-clients.txt index 2d485de..8819c90 100644
>> --- a/Documentation/email-clients.txt
>> +++ b/Documentation/email-clients.txt
>> @@ -79,17 +79,27 @@ to insert into the message.
>>  ~~
>>  Claws Mail (GUI)
>>  
>> -Works. Some people use this successfully for patches.
>> +Tested and Works as of December 2015. Some people use this successfully
>> +for patches.
> 
> Not sure we need datestamps like this here.  In any case, a few kernel
> developers are known to use claws - myself included.  We test it every day :)
> 
>>  To insert a patch use Message->Insert File (CTRL+i) or an external
>> editor. 
>>  If the inserted patch has to be edited in the Claws composition window
>>  "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
>> should be -disabled.
>> +disabled. Also, under the heading "View", sub-heading "Character
>> Encoding" +, choose "Unicode (UTF - 8)"
>> +
>> +Do remember that if you insert or type something in the main text area,
>> +and decide to delete it, you will need to reset the formatting by
>> opening +a new window for the change you want to make. Re-using the
>> window in which +you deleted the text will lead to the new message
>> being mangled. 
> 
> ...and this makes no sense to me.  I've never seen any such behavior in
> claws?
> 
>>  Evolution (GUI)
>>  
>> +As of December 2015, the composing & inserting  method described below
>> +does not work.
> 
> Could it really be that nobody is using evolution?  Much nicer here would
> be to describe how it fails to work, and, ideally, come up with a fix.
> 
>>  Some people use this successfully for patches.
>>  
>>  When composing mail select: Preformat
>> @@ -244,8 +254,9 @@ Sylpheed (GUI)
>>  ~~
>>  Thunderbird (GUI)
>>  
>> -Thunderbird is an Outlook clone that likes to mangle text, but there
>> are ways -to coerce it into behaving.
>> +Thunderbird is an Outlook clone that likes to mangle text, but there
>> are +ways to coerce it into behaving. In December 2015, the internal
>> editor +options do not appear to work.
> 
> Again, what's the problem here?  I suspect there are people using
> Thunderbird out there, how are they doing it if the documented approach
> doesn't work?

I use thunderbird with an external editor plugin, so I just insert patches with
the external editor.


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Sanidhya Solanki]

[PATCH] Documentation: email-clients.txt

The information for Claws Mail, Evolution and Thunderbird was out of
date. It has been updated with new instructions and warnings.

Signed-off-by: Sanidhya Solanki <jpage.l...@gmail.com>
---
 Documentation/email-clients.txt | 19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/Documentation/email-clients.txt
b/Documentation/email-clients.txt index 2d485de..8819c90 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -79,17 +79,27 @@ to insert into the message.
 ~~
 Claws Mail (GUI)
 
-Works. Some people use this successfully for patches.
+Tested and Works as of December 2015. Some people use this successfully
+for patches.
 
 To insert a patch use Message->Insert File (CTRL+i) or an external
editor. 
 If the inserted patch has to be edited in the Claws composition window
 "Auto wrapping" in Configuration->Preferences->Compose->Wrapping
should be -disabled.
+disabled. Also, under the heading "View", sub-heading "Character
Encoding" +, choose "Unicode (UTF - 8)"
+
+Do remember that if you insert or type something in the main text area,
+and decide to delete it, you will need to reset the formatting by
opening +a new window for the change you want to make. Re-using the
window in which +you deleted the text will lead to the new message
being mangled. 
 ~~
 Evolution (GUI)
 
+As of December 2015, the composing & inserting  method described below
+does not work.
+
 Some people use this successfully for patches.
 
 When composing mail select: Preformat
@@ -244,8 +254,9 @@ Sylpheed (GUI)
 ~~
 Thunderbird (GUI)
 
-Thunderbird is an Outlook clone that likes to mangle text, but there
are ways -to coerce it into behaving.
+Thunderbird is an Outlook clone that likes to mangle text, but there
are +ways to coerce it into behaving. In December 2015, the internal
editor +options do not appear to work.
 
 - Allow use of an external editor:
   The easiest thing to do with Thunderbird and patches is to use an
-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Randy Dunlap]

On 12/06/15 20:13, Joe Perches wrote:
> On Sun, 2015-12-06 at 19:10 -0500, Sanidhya Solanki wrote:
>> Try the patch I just send you.
> 
> I think you should first try the patch you just sent yourself.
> 

Yes, it appears to be mangled. :(


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Sanidhya Solanki]

So, now that everyone has sounded off about their clients, I guess we
can know how people still use the clients that are included in the
documentation.

As a side note, JC, I think I have figured out why the patch did not
apply for you but works for me. It appears, ostensibly, that when
using CLaws 3.12 on Fedora, I can send patches that seem to work only
after inserting the file. If I add anything in the compose window after
inserting the patch, the client appears to mangle it. That would
explain the issues you experienced and  I still seem to be having. 

As an aside, I do send every patch to myself on multiple accounts using
Claws, then compare the SHA512 hash, and as a final measure reset git
and reapply the patch. Only then do I send it to the mailing list.

If no one else provides a patch including the information supplied by
this email chain in 5 days, then I will collect it all and send it to
you in a patch.

Best give people a few days to claim their findings as their own,
without delaying it too much.

Try the patch I just send you.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: email-clients.txt

[Joe Perches]

On Sun, 2015-12-06 at 19:10 -0500, Sanidhya Solanki wrote:
> Try the patch I just send you.

I think you should first try the patch you just sent yourself.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Steven Rostedt]

On Thu, 5 Nov 2015 14:11:48 -0500
Chris Metcalf  wrote:

> On 11/05/2015 01:31 PM, Jonathan Corbet wrote:
> > On Fri, 23 Oct 2015 12:13:01 -0400
> > Chris Metcalf  wrote:
> >
> >> +When manually adding In-Reply-To: headers to a patch (e.g., using `git
> >> +send email`), use common sense to associate the patch with previous
> >> +relevant discussion, e.g. link a bug fix to the email with the bug report.
> >> +For a multi-patch series, it is generally best to avoid using
> >> +In-Reply-To: to link to older versions of the series.  This way
> >> +multiple versions of the patch don't become an unmanageable forest of
> >> +references in email clients.  If a link is helpful, you can use an
> >> +"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
> >> +text) to link to an earlier version of the patch series.
> > So this is sitting in my docs folder waiting to see if anybody else had
> > anything to say.  Nope.  I guess I'm not opposed to this addition, but
> > I'm not quite sure what problem is being solved.  Is there a plague of
> > inappropriate hand-crafted In-Reply-To headers out there that I've not
> > seen?
> 
> The "git help send-email" documentation for "--in-reply-to" suggests
> building hand-crafted In-Reply-To headers this way for subsequent
> versions of patch series. This paragraph is intended to suggest that's
> a bad idea.
> 
> > Beyond that, this seems like advice that is better put into
> > SubmittingPatches if we really want it.
> 
> That was my original thought, but Peter suggested email-clients.txt:
> 
> lkml.kernel.org/r/20151023090459.gw17...@twins.programming.kicks-ass.net
> 

Peter said "maybe". I would think keeping this in SubmittingPatches
would be better, as that's the one place we point people to to read
(and I should re-read).

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Chris Metcalf]

On 11/05/2015 01:31 PM, Jonathan Corbet wrote:

On Fri, 23 Oct 2015 12:13:01 -0400
Chris Metcalf  wrote:


+When manually adding In-Reply-To: headers to a patch (e.g., using `git
+send email`), use common sense to associate the patch with previous
+relevant discussion, e.g. link a bug fix to the email with the bug report.
+For a multi-patch series, it is generally best to avoid using
+In-Reply-To: to link to older versions of the series.  This way
+multiple versions of the patch don't become an unmanageable forest of
+references in email clients.  If a link is helpful, you can use an
+"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
+text) to link to an earlier version of the patch series.

So this is sitting in my docs folder waiting to see if anybody else had
anything to say.  Nope.  I guess I'm not opposed to this addition, but
I'm not quite sure what problem is being solved.  Is there a plague of
inappropriate hand-crafted In-Reply-To headers out there that I've not
seen?


The "git help send-email" documentation for "--in-reply-to" suggests
building hand-crafted In-Reply-To headers this way for subsequent
versions of patch series. This paragraph is intended to suggest that's
a bad idea.


Beyond that, this seems like advice that is better put into
SubmittingPatches if we really want it.


That was my original thought, but Peter suggested email-clients.txt:

lkml.kernel.org/r/20151023090459.gw17...@twins.programming.kicks-ass.net

--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Jonathan Corbet]

On Fri, 23 Oct 2015 12:13:01 -0400
Chris Metcalf  wrote:

> +When manually adding In-Reply-To: headers to a patch (e.g., using `git
> +send email`), use common sense to associate the patch with previous
> +relevant discussion, e.g. link a bug fix to the email with the bug report.
> +For a multi-patch series, it is generally best to avoid using
> +In-Reply-To: to link to older versions of the series.  This way
> +multiple versions of the patch don't become an unmanageable forest of
> +references in email clients.  If a link is helpful, you can use an
> +"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
> +text) to link to an earlier version of the patch series.

So this is sitting in my docs folder waiting to see if anybody else had
anything to say.  Nope.  I guess I'm not opposed to this addition, but
I'm not quite sure what problem is being solved.  Is there a plague of
inappropriate hand-crafted In-Reply-To headers out there that I've not
seen?

Beyond that, this seems like advice that is better put into
SubmittingPatches if we really want it.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Steven Rostedt]

On Thu, 5 Nov 2015 14:11:48 -0500
Chris Metcalf  wrote:

> On 11/05/2015 01:31 PM, Jonathan Corbet wrote:
> > On Fri, 23 Oct 2015 12:13:01 -0400
> > Chris Metcalf  wrote:
> >
> >> +When manually adding In-Reply-To: headers to a patch (e.g., using `git
> >> +send email`), use common sense to associate the patch with previous
> >> +relevant discussion, e.g. link a bug fix to the email with the bug report.
> >> +For a multi-patch series, it is generally best to avoid using
> >> +In-Reply-To: to link to older versions of the series.  This way
> >> +multiple versions of the patch don't become an unmanageable forest of
> >> +references in email clients.  If a link is helpful, you can use an
> >> +"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
> >> +text) to link to an earlier version of the patch series.
> > So this is sitting in my docs folder waiting to see if anybody else had
> > anything to say.  Nope.  I guess I'm not opposed to this addition, but
> > I'm not quite sure what problem is being solved.  Is there a plague of
> > inappropriate hand-crafted In-Reply-To headers out there that I've not
> > seen?
> 
> The "git help send-email" documentation for "--in-reply-to" suggests
> building hand-crafted In-Reply-To headers this way for subsequent
> versions of patch series. This paragraph is intended to suggest that's
> a bad idea.
> 
> > Beyond that, this seems like advice that is better put into
> > SubmittingPatches if we really want it.
> 
> That was my original thought, but Peter suggested email-clients.txt:
> 
> lkml.kernel.org/r/20151023090459.gw17...@twins.programming.kicks-ass.net
> 

Peter said "maybe". I would think keeping this in SubmittingPatches
would be better, as that's the one place we point people to to read
(and I should re-read).

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Jonathan Corbet]

On Fri, 23 Oct 2015 12:13:01 -0400
Chris Metcalf  wrote:

> +When manually adding In-Reply-To: headers to a patch (e.g., using `git
> +send email`), use common sense to associate the patch with previous
> +relevant discussion, e.g. link a bug fix to the email with the bug report.
> +For a multi-patch series, it is generally best to avoid using
> +In-Reply-To: to link to older versions of the series.  This way
> +multiple versions of the patch don't become an unmanageable forest of
> +references in email clients.  If a link is helpful, you can use an
> +"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
> +text) to link to an earlier version of the patch series.

So this is sitting in my docs folder waiting to see if anybody else had
anything to say.  Nope.  I guess I'm not opposed to this addition, but
I'm not quite sure what problem is being solved.  Is there a plague of
inappropriate hand-crafted In-Reply-To headers out there that I've not
seen?

Beyond that, this seems like advice that is better put into
SubmittingPatches if we really want it.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Chris Metcalf]

On 11/05/2015 01:31 PM, Jonathan Corbet wrote:

On Fri, 23 Oct 2015 12:13:01 -0400
Chris Metcalf  wrote:


+When manually adding In-Reply-To: headers to a patch (e.g., using `git
+send email`), use common sense to associate the patch with previous
+relevant discussion, e.g. link a bug fix to the email with the bug report.
+For a multi-patch series, it is generally best to avoid using
+In-Reply-To: to link to older versions of the series.  This way
+multiple versions of the patch don't become an unmanageable forest of
+references in email clients.  If a link is helpful, you can use an
+"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
+text) to link to an earlier version of the patch series.

So this is sitting in my docs folder waiting to see if anybody else had
anything to say.  Nope.  I guess I'm not opposed to this addition, but
I'm not quite sure what problem is being solved.  Is there a plague of
inappropriate hand-crafted In-Reply-To headers out there that I've not
seen?


The "git help send-email" documentation for "--in-reply-to" suggests
building hand-crafted In-Reply-To headers this way for subsequent
versions of patch series. This paragraph is intended to suggest that's
a bad idea.


Beyond that, this seems like advice that is better put into
SubmittingPatches if we really want it.


That was my original thought, but Peter suggested email-clients.txt:

lkml.kernel.org/r/20151023090459.gw17...@twins.programming.kicks-ass.net

--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Chris Metcalf]

In-Reply-To: <20151023090459.gw17...@twins.programming.kicks-ass.net>

This commit adds a paragraph suggesting best practices for
when to link patches to previous LKML messages via In-Reply-To.

Signed-off-by: Chris Metcalf 
---
 Documentation/email-clients.txt | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 3fa450881ecb..547c54a2f4e0 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -39,6 +39,16 @@ you avoid some possible charset problems.
 Email clients should generate and maintain References: or In-Reply-To:
 headers so that mail threading is not broken.
 
+When manually adding In-Reply-To: headers to a patch (e.g., using `git
+send email`), use common sense to associate the patch with previous
+relevant discussion, e.g. link a bug fix to the email with the bug report.
+For a multi-patch series, it is generally best to avoid using
+In-Reply-To: to link to older versions of the series.  This way
+multiple versions of the patch don't become an unmanageable forest of
+references in email clients.  If a link is helpful, you can use an
+"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
+text) to link to an earlier version of the patch series.
+
 Copy-and-paste (or cut-and-paste) usually does not work for patches
 because tabs are converted to spaces.  Using xclipboard, xclip, and/or
 xcutsel may work, but it's best to test this for yourself or just avoid
-- 
2.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: discuss In-Reply-To

[Chris Metcalf]

In-Reply-To: <20151023090459.gw17...@twins.programming.kicks-ass.net>

This commit adds a paragraph suggesting best practices for
when to link patches to previous LKML messages via In-Reply-To.

Signed-off-by: Chris Metcalf 
---
 Documentation/email-clients.txt | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 3fa450881ecb..547c54a2f4e0 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -39,6 +39,16 @@ you avoid some possible charset problems.
 Email clients should generate and maintain References: or In-Reply-To:
 headers so that mail threading is not broken.
 
+When manually adding In-Reply-To: headers to a patch (e.g., using `git
+send email`), use common sense to associate the patch with previous
+relevant discussion, e.g. link a bug fix to the email with the bug report.
+For a multi-patch series, it is generally best to avoid using
+In-Reply-To: to link to older versions of the series.  This way
+multiple versions of the patch don't become an unmanageable forest of
+references in email clients.  If a link is helpful, you can use an
+"http://lkml.kernel.org/r/MESSAGEID; URL (e.g., in the cover email
+text) to link to an earlier version of the patch series.
+
 Copy-and-paste (or cut-and-paste) usually does not work for patches
 because tabs are converted to spaces.  Using xclipboard, xclip, and/or
 xcutsel may work, but it's best to test this for yourself or just avoid
-- 
2.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: remove trailing whitespace

[Jonathan Corbet]

On Tue, 29 Sep 2015 14:15:33 +0100
Luis de Bethencourt  wrote:

> While reading Documentation/email-clients.txt to configure my email
> client for Linux kernel development I noticed one of the recent changes
> in the Thunderbird section has a trailing whitespace.

Applied to the docs tree, thanks.

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: remove trailing whitespace

[Jonathan Corbet]

On Tue, 29 Sep 2015 14:15:33 +0100
Luis de Bethencourt  wrote:

> While reading Documentation/email-clients.txt to configure my email
> client for Linux kernel development I noticed one of the recent changes
> in the Thunderbird section has a trailing whitespace.

Applied to the docs tree, thanks.

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: remove trailing whitespace

[Luis de Bethencourt]

Signed-off-by: Luis de Bethencourt 
---

Hi,

While reading Documentation/email-clients.txt to configure my email
client for Linux kernel development I noticed one of the recent changes
in the Thunderbird section has a trailing whitespace.

This is a patch to remove it.

Thanks,
Luis

 Documentation/email-clients.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 3fa4508..aba85b3 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -220,7 +220,7 @@ to coerce it into behaving.
   Compose dialog.
 
   Please note that "external editor" requires that your editor must not
-  fork, or in other words, the editor must not return before closing. 
+  fork, or in other words, the editor must not return before closing.
   You may have to pass additional flags or change the settings of your
   editor. Most notably if you are using gvim then you must pass the -f
   option to gvim by putting "/usr/bin/gvim -f" (if the binary is in
-- 
2.5.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: remove trailing whitespace

[Luis de Bethencourt]

Signed-off-by: Luis de Bethencourt 
---

Hi,

While reading Documentation/email-clients.txt to configure my email
client for Linux kernel development I noticed one of the recent changes
in the Thunderbird section has a trailing whitespace.

This is a patch to remove it.

Thanks,
Luis

 Documentation/email-clients.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 3fa4508..aba85b3 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -220,7 +220,7 @@ to coerce it into behaving.
   Compose dialog.
 
   Please note that "external editor" requires that your editor must not
-  fork, or in other words, the editor must not return before closing. 
+  fork, or in other words, the editor must not return before closing.
   You may have to pass additional flags or change the settings of your
   editor. Most notably if you are using gvim then you must pass the -f
   option to gvim by putting "/usr/bin/gvim -f" (if the binary is in
-- 
2.5.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: Fix one grammar mistake, add extra info about TB

[Jonathan Corbet]

On Mon,  9 Mar 2015 03:53:45 +0200
Giedrius Statkevičius  wrote:

> Fix one grammar mistake (Allows->Allow) and add extra information about
> the external editor add-on of Thunderbird

Applied to the docs tree, thanks.

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: Fix one grammar mistake, add extra info about TB

[Jonathan Corbet]

On Mon,  9 Mar 2015 03:53:45 +0200
Giedrius Statkevičius giedrius.statkevic...@gmail.com wrote:

 Fix one grammar mistake (Allows-Allow) and add extra information about
 the external editor add-on of Thunderbird

Applied to the docs tree, thanks.

jon
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: Fix one grammar mistake, add extra info about TB

[Giedrius Statkevičius]

Fix one grammar mistake (Allows->Allow) and add extra information about
the external editor add-on of Thunderbird: the developer must make sure
that their editor doesn't fork (IOW it mustn't return before closing)
thus they should be careful how they configure the addon. Furthermore,
add a tip how to do it with gvim.

Signed-off-by: Giedrius Statkevičius 
---
 Documentation/email-clients.txt | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index eede608..064eed5 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -211,13 +211,20 @@ Thunderbird (GUI)
 Thunderbird is an Outlook clone that likes to mangle text, but there are ways
 to coerce it into behaving.

-- Allows use of an external editor:
+- Allow use of an external editor:
   The easiest thing to do with Thunderbird and patches is to use an
   "external editor" extension and then just use your favorite $EDITOR
   for reading/merging patches into the body text.  To do this, download
   and install the extension, then add a button for it using
   View->Toolbars->Customize... and finally just click on it when in the
   Compose dialog.
+  Please note that "external editor" requires that your editor must not fork, 
or
+  in other words, the editor must not return before closing thus you may have 
to
+  pass additional flags or change the settings of your editor. Most notably if
+  you are using gvim then you must pass the -f option to gvim by putting
+  "/usr/bin/gvim -f" (if the binary is in /usr/bin) to the text editor field in
+  "external editor" settings. If you are using some other editor then please
+  read its manual to find out how to do this.

 To beat some sense out of the internal editor, do this:

--
2.3.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: Fix one grammar mistake, add extra info about TB

[Giedrius Statkevičius]

Fix one grammar mistake (Allows-Allow) and add extra information about
the external editor add-on of Thunderbird: the developer must make sure
that their editor doesn't fork (IOW it mustn't return before closing)
thus they should be careful how they configure the addon. Furthermore,
add a tip how to do it with gvim.

Signed-off-by: Giedrius Statkevičius giedrius.statkevic...@gmail.com
---
 Documentation/email-clients.txt | 9 -
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index eede608..064eed5 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -211,13 +211,20 @@ Thunderbird (GUI)
 Thunderbird is an Outlook clone that likes to mangle text, but there are ways
 to coerce it into behaving.

-- Allows use of an external editor:
+- Allow use of an external editor:
   The easiest thing to do with Thunderbird and patches is to use an
   external editor extension and then just use your favorite $EDITOR
   for reading/merging patches into the body text.  To do this, download
   and install the extension, then add a button for it using
   View-Toolbars-Customize... and finally just click on it when in the
   Compose dialog.
+  Please note that external editor requires that your editor must not fork, 
or
+  in other words, the editor must not return before closing thus you may have 
to
+  pass additional flags or change the settings of your editor. Most notably if
+  you are using gvim then you must pass the -f option to gvim by putting
+  /usr/bin/gvim -f (if the binary is in /usr/bin) to the text editor field in
+  external editor settings. If you are using some other editor then please
+  read its manual to find out how to do this.

 To beat some sense out of the internal editor, do this:

--
2.3.2

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Jonathan Corbet]

On Tue, 2 Dec 2014 08:10:48 +0100
Richard Leitner  wrote:

> Should I change the patch to something like:
> 
> To insert a patch use Message->Insert File (CTRL+i) or an external
> editor.
> If the inserted patch has to be edited in the Claws composition window
> Auto wrapping in Configuration->Preferences->Compose->Wrapping should
> be disabled.
> 
> Or should I resend the patch without any hint to the auto wrapping?

The former looks good; it's worth a mention in case somebody does decide
to edit their patches on the way out.  Send a new patch (soon for 3.19)
and I'll apply it.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Jonathan Corbet]

On Tue, 2 Dec 2014 08:10:48 +0100
Richard Leitner d...@g0hl1n.net wrote:

 Should I change the patch to something like:
 
 To insert a patch use Message-Insert File (CTRL+i) or an external
 editor.
 If the inserted patch has to be edited in the Claws composition window
 Auto wrapping in Configuration-Preferences-Compose-Wrapping should
 be disabled.
 
 Or should I resend the patch without any hint to the auto wrapping?

The former looks good; it's worth a mention in case somebody does decide
to edit their patches on the way out.  Send a new patch (soon for 3.19)
and I'll apply it.

Thanks,

jon
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Richard Leitner]

Hi jon,
thanks for your reply.

On Mon, 1 Dec 2014 17:34:05 -0500
Jonathan Corbet  wrote:

> Interesting, I've sent an awful lot of patches with claws and I have
> wrapping (a useful feature) enabled.  I can't see it being a problem
> unless you're writing the patch itself in the claws composition
> window...and that would lead to other problems...?

You are right. I had the Auto wrapping disabled because it once messed
up a patch I was editing in the claws composition window. But in
general it works with Auto wrapping enabled. Sorry for that.

Should I change the patch to something like:

To insert a patch use Message->Insert File (CTRL+i) or an external
editor.
If the inserted patch has to be edited in the Claws composition window
Auto wrapping in Configuration->Preferences->Compose->Wrapping should
be disabled.

Or should I resend the patch without any hint to the auto wrapping?

best regards,
richard 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Jonathan Corbet]

On Mon, 1 Dec 2014 23:02:08 +0100
Richard Leitner  wrote:

> Claws Mail GUI client works when "Auto wrapping" is disabled.

Interesting, I've sent an awful lot of patches with claws and I have
wrapping (a useful feature) enabled.  I can't see it being a problem
unless you're writing the patch itself in the claws composition
window...and that would lead to other problems...?

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Richard Leitner]

Claws Mail GUI client works when "Auto wrapping" is disabled.

Signed-off-by: Richard Leitner 
---
 Documentation/email-clients.txt | 9 +
 1 file changed, 9 insertions(+)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 9af538be..1f8929e 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -77,6 +77,15 @@ should appear, and then pressing CTRL-R let you specify the 
patch file
 to insert into the message.
 
 ~~
+Claws Mail (GUI)
+
+Some people use this successfully for patches.
+
+Just turn off Auto wrapping in Configuration->Preferences->Compose->Wrapping
+
+To insert a patch use Message->Insert File (CTRL+i) or an external editor.
+
+~~
 Evolution (GUI)
 
 Some people use this successfully for patches.
-- 
2.1.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Richard Leitner]

Claws Mail GUI client works when Auto wrapping is disabled.

Signed-off-by: Richard Leitner d...@g0hl1n.net
---
 Documentation/email-clients.txt | 9 +
 1 file changed, 9 insertions(+)

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 9af538be..1f8929e 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -77,6 +77,15 @@ should appear, and then pressing CTRL-R let you specify the 
patch file
 to insert into the message.
 
 ~~
+Claws Mail (GUI)
+
+Some people use this successfully for patches.
+
+Just turn off Auto wrapping in Configuration-Preferences-Compose-Wrapping
+
+To insert a patch use Message-Insert File (CTRL+i) or an external editor.
+
+~~
 Evolution (GUI)
 
 Some people use this successfully for patches.
-- 
2.1.3

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Jonathan Corbet]

On Mon, 1 Dec 2014 23:02:08 +0100
Richard Leitner d...@g0hl1n.net wrote:

 Claws Mail GUI client works when Auto wrapping is disabled.

Interesting, I've sent an awful lot of patches with claws and I have
wrapping (a useful feature) enabled.  I can't see it being a problem
unless you're writing the patch itself in the claws composition
window...and that would lead to other problems...?

jon
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation/email-clients.txt: add info about Claws Mail

[Richard Leitner]

Hi jon,
thanks for your reply.

On Mon, 1 Dec 2014 17:34:05 -0500
Jonathan Corbet cor...@lwn.net wrote:

 Interesting, I've sent an awful lot of patches with claws and I have
 wrapping (a useful feature) enabled.  I can't see it being a problem
 unless you're writing the patch itself in the claws composition
 window...and that would lead to other problems...?

You are right. I had the Auto wrapping disabled because it once messed
up a patch I was editing in the claws composition window. But in
general it works with Auto wrapping enabled. Sorry for that.

Should I change the patch to something like:

To insert a patch use Message-Insert File (CTRL+i) or an external
editor.
If the inserted patch has to be edited in the Claws composition window
Auto wrapping in Configuration-Preferences-Compose-Wrapping should
be disabled.

Or should I resend the patch without any hint to the auto wrapping?

best regards,
richard 

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] Documentation/email-clients.txt: add a section about git

[Dan Carpenter]

On Wed, May 07, 2014 at 09:06:54AM -0700, Laura Abbott wrote:
> On 5/7/2014 4:17 AM, Dan Carpenter wrote:
> > These days most people don't use git to send patches so I have added a
> > section about that.
> > 
> 
> Do you mean most people *do* use git to send patches? Or most people don't
> use e-mail clients?

Gar...  Of course.  I'll resend.

regards,
dan carpenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] Documentation/email-clients.txt: add a section about git

[Laura Abbott]

On 5/7/2014 4:17 AM, Dan Carpenter wrote:
> These days most people don't use git to send patches so I have added a
> section about that.
> 

Do you mean most people *do* use git to send patches? Or most people don't
use e-mail clients?

Laura

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[patch] Documentation/email-clients.txt: add a section about git

[Dan Carpenter]

These days most people don't use git to send patches so I have added a
section about that.

Signed-off-by: Dan Carpenter 

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 4e30eba..9004a5fd 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -1,6 +1,17 @@
 Email clients info for Linux
 ==
 
+Git
+--
+These days most developers use `git send-email` instead of regular
+email clients.  On the receiving end, maintainers use `git am` to
+apply the patches.
+
+If you are new to git then send your first patch to yourself.  Save it
+as raw text including all the headers.  Run `cat raw_email.txt | git am`
+and then review the changelog with `git log -p`.  When that works then
+send the patch to list.
+
 General Preferences
 --
 Patches for the Linux kernel are submitted via email, preferably as
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[patch] Documentation/email-clients.txt: add a section about git

[Dan Carpenter]

These days most people don't use git to send patches so I have added a
section about that.

Signed-off-by: Dan Carpenter dan.carpen...@oracle.com

diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 4e30eba..9004a5fd 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -1,6 +1,17 @@
 Email clients info for Linux
 ==
 
+Git
+--
+These days most developers use `git send-email` instead of regular
+email clients.  On the receiving end, maintainers use `git am` to
+apply the patches.
+
+If you are new to git then send your first patch to yourself.  Save it
+as raw text including all the headers.  Run `cat raw_email.txt | git am`
+and then review the changelog with `git log -p`.  When that works then
+send the patch to list.
+
 General Preferences
 --
 Patches for the Linux kernel are submitted via email, preferably as
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] Documentation/email-clients.txt: add a section about git

[Laura Abbott]

On 5/7/2014 4:17 AM, Dan Carpenter wrote:
 These days most people don't use git to send patches so I have added a
 section about that.
 

Do you mean most people *do* use git to send patches? Or most people don't
use e-mail clients?

Laura

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] Documentation/email-clients.txt: add a section about git

[Dan Carpenter]

On Wed, May 07, 2014 at 09:06:54AM -0700, Laura Abbott wrote:
 On 5/7/2014 4:17 AM, Dan Carpenter wrote:
  These days most people don't use git to send patches so I have added a
  section about that.
  
 
 Do you mean most people *do* use git to send patches? Or most people don't
 use e-mail clients?

Gar...  Of course.  I'll resend.

regards,
dan carpenter

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/