patchSuggestion for mailing lists... split [PATCH]-es into own list

I use gmail as my mail client and it doesn't grok 'PATCH' filters (primarily the case of the word).

Are there any of you using Gmail that has managed to get around this issue....?

Perhaps we should have a separate mailing list for patches vs discussion.

Hi,

On Thu, 11 Oct 2007, Thomas Harning Jr. wrote:

That's just another bug in gmail.

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).

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

Hi. Storing binary files as deltas is helpful to keep source and binary files together and in sync So is it possible for git to do that as svn. This is my only pain when using git.

银平 wrote:

Yes, and git does this already in pack files. Maybe you're not seeing it because you haven't packed anything yet. Try to run 'git gc'.

jlh

git-gc works perfectly! Thanks all very much. 

-----Original Message-----
From: Jean-Luc Herren [mailto:jlh@gmx.ch] 
Sent: Friday, October 12, 2007 1:54 AM
To: 银平
Cc: git@vger.kernel.org
Subject: Re: Is it possible for git to support binary differencing for
binary files?

银平 wrote:

Yes, and git does this already in pack files. Maybe you're not seeing it because you haven't packed anything yet. Try to run 'git gc'.

jlh

银平, Thu, Oct 11, 2007 18:37:43 +0200:

Why? Git works perfectly with binary files. In fact, some of my repos have more binaries than text.

On 10/12/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

<aol>mee too! - I think it's the kind of development culture that Linus tries to foster, and I suspect Junio likes too: "talk in patches" which is a lot more productive than "talk like a pirate", bikeshedding and other maladies that can fester in mailing lists.

So no split for me ;-) We have the additional alibi that git users are supposed to be programmers.

m

On 10/11/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Oh? Turning off Rich formatting and copy/pasting the patch from my editor worked for me.

On 10/12/07, Simon Sasburg <simon.sasburg@gmail.com> wrote:

The problem occurs when gmail decides to wrap the lines in the patch (max 72 chars per line, I guess).

-- larsh

On 10/12/07, Lars Hjemli <lh@elementstorage.no> wrote:

Ah, good to know, then.

Hi,

On Fri, 12 Oct 2007, Simon Sasburg wrote:

Really? Even a single space on a single line is retained (last time I checked that did not work)? If so, please amend Documentation/SubmittingPatches.

Ciao, Dscho

Thomas Harning Jr. wrote:

This list is somewhat unusual in that the two are not really distinct. Most of the discussion (or at least a huge percentage of it) is in response to patches or results in patches somewhere along the line, with updated versions of those patches intermingled with feedback. Having to bounce back and forth between two mailing lists for all that would seriously impair the flow of ideas / improvements here.

-Steve

On 11/10/2007, Thomas Harning Jr. <harningt@gmail.com> wrote:

Try this in the 'has the words' box (the whole thing): to:git@vger.kernel.org -("+++ b" subject:"[PATCH")

Obviously get rid of the '-' for the other filter you'll want. Patches that lead to discussion will probably get both tags. The "+++ b" is so you don't class mails that don't have a patch in the body as patch mails.