will be be saved in textfiles named
+
+0001-Introduce-new-Feature.patch
+0002-Improve-Documentation.patch
+
+The first lines of such a file might look like
+
+1 From d39e331c30cb563fd152f484f7ca1d14dc98d57e Mon Sep 17 00:00:00 2001
+2 From: Stefan Beller
+3 Date: Fri, 13 Jul 2012 12:
Stefan Beller writes:
> +5) "git format-patch HEAD~n"
> +
> +Use "git format-patch HEAD~n" to extract the last n patches from your
> +git repository. They will be be saved in textfiles named
> +
> +0001-Introduce-new-Feature.patch
> +0002-Improve-Documentation.patch
Two comments and a ha
On 07/23/2012 12:20 AM, Stefan Beller wrote:
> On 07/23/2012 06:45 AM, Randy Dunlap wrote:
>
>> On 07/22/2012 12:56 AM, Stefan Beller wrote:
>>
>>> Documentation/SubmittingPatches | 191
>>>
>>> 1 file changed, 116 insertions(+), 75 deletions(-)
>>>
>>
On 07/23/2012 06:45 AM, Randy Dunlap wrote:
On 07/22/2012 12:56 AM, Stefan Beller wrote:
Documentation/SubmittingPatches | 191
1 file changed, 116 insertions(+), 75 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/Submittin
On 07/22/2012 12:56 AM, Stefan Beller wrote:
> Documentation/SubmittingPatches | 191
>
> 1 file changed, 116 insertions(+), 75 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index c379a2a..ac00451 10064
"git format-patch HEAD~n"
+
+Use "git format-patch HEAD~n" to extract the last n patches from your
+git repository. They will be be saved in textfiles named
+
+0001-Introduce-new-Feature.patch
+0002-Improve-Documentation.patch
+
+The first lines of such a file might look
On 07/15/2012 11:20 PM, Stefan Beller wrote:
> Heh,
> It seems as if googlemail is not a suited interface to contribute to linux.
>
> The raw patch (without clipped lines) can be found at
> http://pastebin.com/raw.php?i=3QKRZz2M
>
> Stefan
>
> 2012/7/15 Rob Landley :
>> On 07/13/2012 09:45 AM,
Heh,
It seems as if googlemail is not a suited interface to contribute to linux.
The raw patch (without clipped lines) can be found at
http://pastebin.com/raw.php?i=3QKRZz2M
Stefan
2012/7/15 Rob Landley :
> On 07/13/2012 09:45 AM, Stefan Beller wrote:
>> This updates the documentation on how to
On 07/13/2012 09:45 AM, Stefan Beller wrote:
> This updates the documentation on how to create patches and send
> these to the kernel mailing list.
>
> The documentation before was written in times before git was there,
> so the crafting of the patch needed to be done manually by diff -up
> in the
n" to extract the last n patches from your
+git repository. They will be be saved in textfiles named
+
+0001-Introduce-new-Feature.patch
+0002-Improve-Documentation.patch
+
+The first lines of such a file might look like
+
+1 From d39e331c30cb563fd152f484f7ca1d14dc98d57e Mon Sep 17 00:0
On Fri, Jul 13, 2012 at 7:51 AM, Stefan Beller
wrote:
> This updates the documentation on how to create patches and send
> these to the kernel mailing list.
>
> The documentation before was written in times before git was there,
> so the crafting of the patch needed to be done manually by diff -up
On Fri, Jul 13, 2012 at 01:51:50PM +0200, Stefan Beller wrote:
> This updates the documentation on how to create patches and send
> these to the kernel mailing list.
>
> The documentation before was written in times before git was there,
> so the crafting of the patch needed to be done manually by
HEAD~n"
+
+Use "git format-patch HEAD~n" to extract the last n patches from your
+git repository. They will be be saved in textfiles named
+
+0001-Introduce-new-Feature.patch
+0002-Improve-Documentation.patch
+
+The first lines of such a file might look like
+
+1 From d39e331c30
13 matches
Mail list logo