From: Jakub Narebski <jnareb@gmail.com>
To: "Rob Shearman" <robertshearman@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] imap-send.c: Clean up coding style to better match the rest of the git codebase.
Date: Mon, 07 Jul 2008 05:40:16 -0700 (PDT) [thread overview]
Message-ID: <m3zloteukz.fsf@localhost.localdomain> (raw)
In-Reply-To: <1096648c0807070517o8f22f0cs4d25103675bd635d@mail.gmail.com>
"Rob Shearman" <robertshearman@gmail.com> writes:
> 2008/7/7 Junio C Hamano <gitster@pobox.com>:
> > These patches seem to have been linewrapped severely. I _could_ fix them
> > up and apply, but the last one being about whitespace and style fixes, I'd
> > rather not.
>
> 2008/6/22 Junio C Hamano <gitster@pobox.com>:
> > Next time please do _not_ attach *.diff but follow the style of patch
> > submission other people do (see recent patch from Linus for example).
>
> How do you propose I fix this? I attached the patch last time to avoid
> the problem of line wrapping.
If possible to turn of linewrapping, or use either git-send-email
(I think you can send patches also via Gmail) or git-imap-send,
then preferred solution is to have patch inline.
If it is not possible, then attach the patch, but preferrably
1) with text/plain mimetype (.txt extension instead of .patch or
.diff could be required for that)
2) 8bit (preferred) or quoted-printable (if 8bit is not possible)
transfer encoding (base64 is terrible waste of space); text/plain
should chose quoted-printable at worst
3) use "inline" attachement (select 'suggest to display attachement'
or something like that), so it is possible to select attachement
and hit reply.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-07-07 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 8:05 [PATCH 3/3] imap-send.c: Clean up coding style to better match the rest of the git codebase Rob Shearman
2008-07-07 8:49 ` Junio C Hamano
2008-07-07 12:17 ` Rob Shearman
2008-07-07 12:40 ` Jakub Narebski [this message]
2008-07-08 23:21 ` Rob Shearman
2008-07-12 12:38 ` Jakub Narebski
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=m3zloteukz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robertshearman@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.