ignore Documentation/DocBook/media/
Subsystems (2)
PATCH 1/1 ignore Documentation/DocBook/media/
Quoted 1 line
From
81a09633855b88d19f013d7e559e0c4f602ba711Mon Sep 17 00:00:00 2001
From: Michael Jones <[email protected]>
Date: Thu, 10 Mar 2011 16:16:38 +0100
Subject: [PATCH] ignore Documentation/DocBook/media/
It is created and populated by 'make htmldocs'
--- Documentation/DocBook/.gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
Documentation/DocBook/.gitignore +1 -0
@@ -8,3 +8,4 @@ *.dvi *.log *.out +media/
Signature · 6 lines
1.7.4.1 MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
Hi Michael,
Thanks for the patch.
Quoted 9 lines · On Wednesday 16 March 2011 15:22:53 Michael Jones wrote:
From
81a09633855b88d19f013d7e559e0c4f602ba711Mon Sep 17 00:00:00 2001
From: Michael Jones <[email protected]>
Date: Thu, 10 Mar 2011 16:16:38 +0100
Subject: [PATCH] ignoreDocumentation/DocBook/media/It is created and populated by 'make htmldocs'
Signed-off-by Michael Jones <[email protected]>
Quoted 13 lines
--- Documentation/DocBook/.gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)(quoted diff) +0
-0b/Documentation/DocBook/.gitignore index c6def35..679034c 100644
Documentation/DocBook/.gitignore +1
-0@@ -8,3 +8,4 @@ *.dvi *.log *.out +media/
Signature · 3 lines
Regards, Laurent Pinchart
Quoted 18 lines · Michael Jones
Quoted 1 line
From
81a09633855b88d19f013d7e559e0c4f602ba711Mon Sep 17 00:00:00 2001From: Michael Jones <[email protected]>
Date: Thu, 10 Mar 2011 16:16:38 +0100
Subject: [PATCH] ignoreDocumentation/DocBook/media/It is created and populated by 'make htmldocs'
Signed-off-by Michael Jones <[email protected]>--- Documentation/DocBook/.gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)Documentation/DocBook/.gitignore +0
-0
Documentation/DocBook/.gitignore line 11
Quoted 4 lines
Documentation/DocBook/.gitignore +1
-0@@ -8,3 +8,4 @@ *.dvi *.log *.out +media/
In general, where do patches on this list land? On
http://linuxtv.org/wiki/index.php/Developer_Section
the link to "Current git log" is broken. The link to 'Git V4L-DVB development repository' is v4l-dvb.git which is suspiciously inactive:
2.6.37-rc8, from 2 months ago. Judging by the activity level, I guess that patches from this mailing list currently land in branch 'staging/for_v2.6.39' of 'http://git.linuxtv.org/media_tree.git'?
And what's the destiny of this patch in particular? It doesn't seem to have even been picked up by patchwork.
thanks,
Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
Em 24-03-2011 12:34, Michael Jones escreveu:
Quoted 24 lines · Michael Jones
Quoted 18 lines
Quoted 1 line
From
81a09633855b88d19f013d7e559e0c4f602ba711Mon Sep 17 00:00:00 2001From: Michael Jones <[email protected]>
Date: Thu, 10 Mar 2011 16:16:38 +0100
Subject: [PATCH] ignoreDocumentation/DocBook/media/It is created and populated by 'make htmldocs'
Signed-off-by Michael Jones <[email protected]>--- Documentation/DocBook/.gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)Documentation/DocBook/.gitignore +0
-0Documentation/DocBook/.gitignore line 11
Quoted 4 lines
Documentation/DocBook/.gitignore +1
-0@@ -8,3 +8,4 @@ *.dvi *.log *.out +media/
Quoted 7 lines
In general, where do patches on this list land? On
http://linuxtv.org/wiki/index.php/Developer_Section
the link to "Current git log" is broken. The link to 'Git V4L-DVB development repository' is v4l-dvb.git which is suspiciously inactive:
2.6.37-rc8, from 2 months ago. Judging by the activity level, I guess that patches from this mailing list currently land in branch 'staging/for_v2.6.39' of 'http://git.linuxtv.org/media_tree.git'?
Yes, that's true (and, probably on next week, it will be at the branch staging/for_v2.6.40 of the same git tree).
If you see anything pointing to the wrong place, please help us fixing it, by editing our wiki or sending us patches.
Quoted 2 lines
And what's the destiny of this patch in particular? It doesn't seem to have even been picked up by patchwork.
Patchwork is subscribed at the linux-media ML. So, every email sent to the ML are analyzed and, if it looks like a patch, it will catch it.
If your patch weren't caught, then one of the following things happened:
1) Patch was broken. Some emailers love to break patches by mangling whitespaces/tabs;
2) The patch is not inlined, but, instead, it is on a mime message,
and the patch has a wrong mime type (the right type is text/x-patch). If the attachment type is text/plain, patchwork will try to get a patch there using some euristics. If the mime type is application/binary (as some really bad non-Linux emailers do), the patch will be silently discarded, as patchwork doesn't know how to handle a binary blob;
3) Some bug at patchwork;
4)The email were not received by patchwork.kernel.org.
Your patch seems correct, so it is probably (3) or (4). One of the common issues for (3) is python bad habit of aborting scripts if they contain a character upper than 127 and the codeset is wrong.
Just try to re-send it to the ML and see if Patchwork will catch.
Cheers,
Mauro