On Wed Sep 13 10:57:33 2006 +0200, Marcus Meissner marcus@beiboot.franken.de wrote:
Mention kernel 2.6.
documentation/README.de | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
10857c3dbb8429ea599288ac93f4cecd8ffeff59 diff --git a/documentation/README.de b/documentation/README.de index c4a1324..680e077 100644 --- a/documentation/README.de +++ b/documentation/README.de @@ -45,7 +45,7 @@ Linux-Info: Obwohl Linux 2.2.x immer noch funktionieren sollte und Linux 2.0.x vielleicht auch noch funktioniert (ältere 2.0.x-Versionen verzeichneten Abstürze im Zusammenhang mit Threads), sollte man am besten einen
- aktuellen Kernel wie 2.4.x verwenden.
- aktuellen Kernel wie 2.4.x oder 2.6.x verwenden.
FreeBSD-Info: Stellen Sie sicher, dass Sie die Optionen USER_LDT, SYSVSHM, SYSVSEM und -- 1.2.4
Hi,
A few of the emails you've sent to the wine-patches mailing list lately have not had 'To:' headers. Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder). It probably means that whatever program you are using to send these emails is broken slightly.
I hope you are able to work it out, n0dalus.
On Wed, Sep 13, 2006 at 09:57:13PM +0930, n0dalus wrote:
On Wed Sep 13 10:57:33 2006 +0200, Marcus Meissner marcus@beiboot.franken.de wrote:
Mention kernel 2.6.
documentation/README.de | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
10857c3dbb8429ea599288ac93f4cecd8ffeff59
Hi,
A few of the emails you've sent to the wine-patches mailing list lately have not had 'To:' headers. Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder). It probably means that whatever program you are using to send these emails is broken slightly.
I hope you are able to work it out,
Its git-format-patch, I just bounce the mails ...
LIkely I need to invest time to understand git patch submission better.
Ciao, Marcus
On Wednesday 13 September 2006 14:49, Marcus Meissner wrote:
A few of the emails you've sent to the wine-patches mailing list lately have not had 'To:' headers. Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder). It probably means that whatever program you are using to send these emails is broken slightly.
It also doesn't set the date.
Its git-format-patch, I just bounce the mails ...
LIkely I need to invest time to understand git patch submission better.
Ah, figures. git-format-patch creates incomplete headers, as it expects you're using this messages as a draft in your email client. Now, I'm not 100% sure how to do that in mutt, but I think mutt will understand a maildir format postponed mailbox. Just try and dump the patches generated by git-format-patch there. (Haven't tried that myself)
Cheers, Kai
On Wed, Sep 13, 2006 at 07:47:31PM +0200, Kai Blin wrote:
On Wednesday 13 September 2006 14:49, Marcus Meissner wrote:
A few of the emails you've sent to the wine-patches mailing list lately have not had 'To:' headers. Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder). It probably means that whatever program you are using to send these emails is broken slightly.
It also doesn't set the date.
Its git-format-patch, I just bounce the mails ...
LIkely I need to invest time to understand git patch submission better.
Ah, figures. git-format-patch creates incomplete headers, as it expects you're using this messages as a draft in your email client. Now, I'm not 100% sure how to do that in mutt, but I think mutt will understand a maildir format postponed mailbox. Just try and dump the patches generated by git-format-patch there. (Haven't tried that myself)
I just did mutt -f 0001-...... bwine-patches...<return>
I guess I should invest time in the imap send stuff ;)
Ciao, Marcus
Marcus Meissner wrote:
On Wed, Sep 13, 2006 at 07:47:31PM +0200, Kai Blin wrote:
On Wednesday 13 September 2006 14:49, Marcus Meissner wrote:
A few of the emails you've sent to the wine-patches mailing list lately have not had 'To:' headers. Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder). It probably means that whatever program you are using to send these emails is broken slightly.
It also doesn't set the date.
Its git-format-patch, I just bounce the mails ...
LIkely I need to invest time to understand git patch submission better.
Ah, figures. git-format-patch creates incomplete headers, as it expects you're using this messages as a draft in your email client. Now, I'm not 100% sure how to do that in mutt, but I think mutt will understand a maildir format postponed mailbox. Just try and dump the patches generated by git-format-patch there. (Haven't tried that myself)
I just did mutt -f 0001-...... bwine-patches...<return>
I guess I should invest time in the imap send stuff ;)
You can add custom email headers in the git config for git-format-patch. There's where i add the "To: wine-patches@winehq.org". Then i just do a mutt -H 0001-..... and send the email normally (not bounce it).
bye michael
On Wed, Sep 13, 2006 at 09:57:13PM +0930, n0dalus wrote:
Many people have their mail clients configured to filter emails into folders based on 'To:' fields, so it would be great if you could sort that out (your last few ones, such as this one, ended up in my inbox instead of my wine folder).
You could filter on "List-Post: mailto:wine-patches@winehq.org" . (Yes there should be a proper To field, but this way it would be more reliable for you regardless how people send their mail.)
Jan