git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>, Michael <barra_cuda@katamail.com>
Subject: Re: [PATCH] Documentation: add KMail in SubmittingPatches
Date: Tue, 6 Feb 2007 14:47:49 +0000	[thread overview]
Message-ID: <200702061447.51459.andyparkins@gmail.com> (raw)
In-Reply-To: <7vveigkmpv.fsf@assigned-by-dhcp.cox.net>

On Tuesday 2007 February 06 03:07, Junio C Hamano wrote:

> I do not use KMail myself, so I cannot comment on the procedure,
> but from the cursory look it *should* do the right thing.  Only
> that it makes me a bit nervous to see your hunk header being
> line wrapped.

I use Kmail for submitting patches, and it seems to work okay.  The important 
thing is to turn word wrap off as soon as you open it.  If you did this:

 * Save patch as draft (say with git-imap-send)
 * Open draft
 * Close draft
 * Open draft
 * Turn word wrap off
 * Send

You would have a badly wrapped patch.  The reason is that until you store the 
email again, kmail seems to know the difference between a hard LF that was in 
the original email and a LF that it inserted to wrap the lines.  So, as soon 
as you turn word wrap off all the soft LFs go away - perfect.  However, if 
you save without turning word wrap off, all those soft LFs become hard and 
the next time you open the email there is no easy way to get the untouched 
email back.

Michael's original instructions seem fine though.  I don't think his word wrap 
problem in this case is the work of KMail.



Andy

-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com

      parent reply	other threads:[~2007-02-06 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03  6:40 Why is it bad to rewind a branch that has already been pushed out? Junio C Hamano
2007-02-03 10:40 ` Andy Parkins
2007-02-03 19:42   ` Junio C Hamano
2007-02-04 18:01     ` Andy Parkins
2007-02-03 13:20 ` Theodore Tso
2007-02-04 16:16 ` Robin Rosenberg
2007-02-04 20:08   ` Junio C Hamano
     [not found]     ` <20070205132150.123659@dial-up-mi-449.lombardiacom.it>
2007-02-05 13:27       ` [PATCH] Documentation: add KMail in SubmittingPatches Michael
2007-02-06  3:07         ` Junio C Hamano
2007-02-06 13:45           ` Michael
2007-02-06 14:16             ` Jakub Narebski
2007-02-06 14:47           ` Andy Parkins [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200702061447.51459.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=barra_cuda@katamail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).