From: "Lars Hjemli" <lh@elementstorage.no>
To: "Simon Sasburg" <simon.sasburg@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Thomas Harning Jr." <harningt@gmail.com>,
git@vger.kernel.org
Subject: Re: Suggestion for mailing lists... split [PATCH]-es into own list
Date: Fri, 12 Oct 2007 10:26:31 +0200 [thread overview]
Message-ID: <8c5c35580710120126x51c300bfu4345b8c6315d953c@mail.gmail.com> (raw)
In-Reply-To: <981e6de60710120027j5f390a9tbe2a4c76db9ed06d@mail.gmail.com>
On 10/12/07, Simon Sasburg <simon.sasburg@gmail.com> wrote:
> On 10/11/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > We did not even find a way to post patches via gmail's web interface, not
> > without severely damaging the patches.
>
> Oh? Turning off Rich formatting and copy/pasting the patch from my
> editor worked for me.
The problem occurs when gmail decides to wrap the lines in the patch
(max 72 chars per line, I guess).
--
larsh
next prev parent reply other threads:[~2007-10-12 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 15:57 Suggestion for mailing lists... split [PATCH]-es into own list Thomas Harning Jr.
2007-10-11 16:07 ` Johannes Schindelin
2007-10-11 16:37 ` Is it possible for git to support binary differencing for binary files? 银平
2007-10-11 17:54 ` Jean-Luc Herren
2007-10-12 3:01 ` franky
2007-10-11 18:15 ` Alex Riesen
2007-10-12 4:50 ` Suggestion for mailing lists... split [PATCH]-es into own list Martin Langhoff
2007-10-12 7:27 ` Simon Sasburg
2007-10-12 8:26 ` Lars Hjemli [this message]
2007-10-12 9:51 ` Simon Sasburg
2007-10-12 10:05 ` Johannes Schindelin
2007-10-11 18:00 ` Steven Grimm
2007-10-11 22:53 ` Baz
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=8c5c35580710120126x51c300bfu4345b8c6315d953c@mail.gmail.com \
--to=lh@elementstorage.no \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=harningt@gmail.com \
--cc=simon.sasburg@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 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).