From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Thomas Harning Jr." <harningt@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Suggestion for mailing lists... split [PATCH]-es into own list
Date: Thu, 11 Oct 2007 17:07:23 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710111704570.4174@racer.site> (raw)
In-Reply-To: <e47324780710110857s472bf099u3e350d17a2c29f78@mail.gmail.com>
Hi,
On Thu, 11 Oct 2007, Thomas Harning Jr. wrote:
> I use gmail as my mail client and it doesn't grok 'PATCH' filters
> (primarily the case of the word).
That's just another bug in gmail.
> Are there any of you using Gmail that has managed to get around this
> issue....?
We did not even find a way to post patches via gmail's web interface, not
without severely damaging the patches. So I guess no, most of us avoid
the web interface (unless absolutely necessary, in which case we resort to
the less than brilliant solution to attach the patches).
> Perhaps we should have a separate mailing list for patches vs
> discussion.
I, for one, am totally opposed to this split. All too often valuable
_user_ discussions turn into _technical_ discussions, and thence into a
throwing back and forth patches.
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-11 16:07 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 [this message]
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
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=Pine.LNX.4.64.0710111704570.4174@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=harningt@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).