linux-kernel - Re: [PATCH 1/1] drivers/staging/pi433: New driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 16 Jul 2017 16:47:57 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Marcus Wolf <marcus.wolf@...f-entwicklungen.de>
Cc:     robh+dt@...nel.org, linux-kernel@...r.kernel.org,
        devel@...verdev.osuosl.org, grant.likely@...aro.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH 1/1] drivers/staging/pi433: New driver

On Sun, Jul 16, 2017 at 03:53:57PM +0200, Marcus Wolf wrote:
> Hi Greg,
>  
> like I wrote before - unfortunally I couldn't find a git command, squashing
> all my commits into one single patch. Therfore I copy and pasted the patch
> manually.

git diff FIRST_PATCH..HEAD > my.patch

will do it.

> Never the less, the first three rows were copied from a patch, originally
> generated by git.
>  
> I used
> git format-patch master --stdout -p > pi433_patch
> for the first rows
> and
> git diff master > pi433_patch
> fot the dif/patch itself.
> 
> If someone could help me with better git commands, I would be happy :-)


The issue is that the header was in the email body, if you use git
send-email, it should not show up.

thanks,

greg k-h