[U-Boot-Users] Posting non-wrapped patches

[U-Boot-Users] Posting non-wrapped patches

[David Saada]

Hi,
As you may have noticed, I've been trying to post some patches, but sending most of them failed due to line wrapping problems. This is a problem with the mailer we use here (outlook). Messing with the mailer didn't help, and so was posting via the Nabble forum or my gmail account in text mode.
I'd appreciate any suggestion from you, as this pretty much holds me back.
Regards,
David.

[U-Boot-Users] Posting non-wrapped patches

[Grant Erickson]

On 5/18/08 4:53 AM, David Saada wrote:
> As you may have noticed, I've been trying to post some patches, but sending
> most of them failed due to line wrapping problems. This is a problem with the
> mailer we use here (outlook). Messing with the mailer didn't help, and so was
> posting via the Nabble forum or my gmail account in text mode.
>
> I'd appreciate any suggestion from you, as this pretty much holds me back.

David,

You want to install 'git send-email':

    http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html

Regards,

Grant Erickson
Principal
Nuovation System Designs, LLC

998 Alpine Terrace Suite 3
Sunnyvale, CA 94086-2469
US

T +1-408-749-0495
F +1-205-449-0495
M +1-408-489-5710

gerickson at nuovations.com
http://www.nuovations.com/

[U-Boot-Users] Posting non-wrapped patches

[David Saada]

>> As you may have noticed, I've been trying to post some patches, but sending
>> most of them failed due to line wrapping problems. This is a problem with the
>> mailer we use here (outlook). Messing with the mailer didn't help, and so was
>> posting via the Nabble forum or my gmail account in text mode.
>>
>> I'd appreciate any suggestion from you, as this pretty much holds me back.



> You want to install 'git send-email':

  <  http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html

Thanks Grant, but this doesn't seem to work with our exchange server. Our company also blocks the access to external SMTP servers (like gmail).
Is there a way to include some sort of attachment via mail, or via a forum, so it can be seen as a text message in the list?
Regards,
David.

[U-Boot-Users] Posting non-wrapped patches

[Jerry Van Baren]

David Saada wrote:
>>> As you may have noticed, I've been trying to post some patches, but sending
>>> most of them failed due to line wrapping problems. This is a problem with the
>>> mailer we use here (outlook). Messing with the mailer didn't help, and so was
>>> posting via the Nabble forum or my gmail account in text mode.
>>>
>>> I'd appreciate any suggestion from you, as this pretty much holds me back.
> 
> 
> 
>> You want to install 'git send-email':
> 
>   <  http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html
> 
> Thanks Grant, but this doesn't seem to work with our exchange server. Our company also blocks the access to external SMTP servers (like gmail).
> Is there a way to include some sort of attachment via mail, or via a forum, so it can be seen as a text message in the list?
> Regards,
> David.

Hi David,

The following is from my limited exposure to Outlook (achoo-sorry).

Option 1:
---------
I've been playing with sending patches using Outlook.  "Properly 
formatted" patches can be done by changing to a monospace font.  This 
can be done either before or after pasting in the patch:

Before pasting in the patch, you can change the format using a monospace 
font and honor the line breaks by selecting the menu option "Format / 
Style / Formatted" and then pasting the patch into that section.

If you forget or misfire on pre-selecting the font, after pasting in the 
patch, you can highlighting the patch and select the menu option "Format 
/ Style / Formatted".

Option 2:
---------
It is possible that your Exchange server supports port 25 (depends how 
what your IT staff configured it).  If this is the case, git-send-email 
will work directly with your Exchange server.

You need to figure out the Exchange server and your user name (including 
the AD domain).

To figure out your Exchange server:
1) In Outlook, select the menu selection Tools/Email Accounts.. which 
brings up a dialog allowing you to "View or change existing e-mail accounts"
2) Click the "Next" button which brings up the next dialog box.
3) Select the "Microsoft Exchange Server" account and click the "Change" 
button.
4) This dialog box shows your Exchange server name.

 From the command line, run
   telnet <exchsvr> 25
and, if you get a prompt, you have port 25 support enabled (good!).

Note that you can use the above information to configure Thunderbird to 
use Exchange via IMAP (IMAP or port 25 for sending) as well. 
Thunderbird isn't (much? any?) better than Outlook for sending patches 
as far as I can tell.  The built in editor line wraps unless you do the 
HTML/preformatted trick the same way as Outlook requires (gag).  The 
linux kernel hints talk about using an external editor with Tbird, but I 
don't see that as an option under Windows.

Best regards,
gvb

[U-Boot-Users] Posting non-wrapped patches

[David Saada]

> Option 1:
> ---------
> I've been playing with sending patches using Outlook.  "Properly
> formatted" patches can be done by changing to a monospace font.  This
> can be done either before or after pasting in the patch:
>
> Before pasting in the patch, you can change the format using a monospace
> font and honor the line breaks by selecting the menu option "Format /
> Style / Formatted" and then pasting the patch into that section.
>
> If you forget or misfire on pre-selecting the font, after pasting in the
> patch, you can highlighting the patch and select the menu option "Format
> / Style / Formatted".
>
> Option 2:
> ---------
> It is possible that your Exchange server supports port 25 (depends how
> what your IT staff configured it).  If this is the case, git-send-email
> will work directly with your Exchange server.
>
> You need to figure out the Exchange server and your user name (including
> the AD domain).
>
> To figure out your Exchange server:
> 1) In Outlook, select the menu selection Tools/Email Accounts.. which
> brings up a dialog allowing you to "View or change existing e-mail
> accounts"
> 2) Click the "Next" button which brings up the next dialog box.
> 3) Select the "Microsoft Exchange Server" account and click the "Change"
> button.
> 4) This dialog box shows your Exchange server name.
>
>  From the command line, run
>    telnet <exchsvr> 25
> and, if you get a prompt, you have port 25 support enabled (good!).
>
> Note that you can use the above information to configure Thunderbird to
> use Exchange via IMAP (IMAP or port 25 for sending) as well.
> Thunderbird isn't (much? any?) better than Outlook for sending patches
> as far as I can tell.  The built in editor line wraps unless you do the
> HTML/preformatted trick the same way as Outlook requires (gag).  The
> linux kernel hints talk about using an external editor with Tbird, but I
> don't see that as an option under Windows.
>
> Best regards,
> gvb

Thanks Jerry. Option 1 did the trick. My mistake was sending the patches using plain text instead of rich text as you had suggested. Gonna repost the patches now - hopefully for the last time.
Regards,
David.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080519/f1a9d668/attachment.htm